fix(#163,#162): list_credits status filter defaults to Active + retire event ordering#174
Open
akindoyinabraham0-collab wants to merge 1 commit into
Conversation
…retire event ordering
|
@akindoyinabraham0-collab Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #163
Closes #162
Summary
Two bugs fixed in a single branch.
Fix #163 —
list_creditsdefaults to Active-onlyRoot cause:
listCreditsincredits.service.tsbuilt its candidate list from a hardcoded empty array, so every filter — including the status filter — was dead code. The endpoint always returned an empty result set.Changes:
credit.repository.ts— addedfindByStatus(status, page, limit)toICreditRepositoryandInMemoryCreditRepository.credits.service.ts—listCreditsnow reads fromcreditRepo.findByStatus(), defaulting toCreditStatus.Activewhen nostatusquery param is supplied. Secondary filters (methodology, geography, vintageYear, tonnes range) are applied in-memory on top.credit.repository.spec.ts— six new tests covering everyCreditStatusvalue (Active,Retired,Flagged,Pending), the empty-result case, and pagination.Fix #162 —
retireemitsCreditRetiredonly after record is persistedRoot cause: No explicit application-level event emission existed, but the method needed a clear enforced ordering guarantee so any future listener could never observe a
CreditRetiredevent without a corresponding record in storage.Changes:
retirement.service.ts— introducedIEventEmitterinterface andEVENT_EMITTERinjection token.retire()now explicitly emitsCreditRetiredafterretirementRepo.save()resolves. If the save throws, the event is never emitted. Ordering guarantee documented in JSDoc.retirement.module.ts— provides a Node.jsEventEmitterinstance bound toEVENT_EMITTER(no new npm dependency).retirement.service.spec.ts— new test file with six tests: save-before-emit order, record exists at emit time, no event on write failure, exactly one event per call, correct payload, record retrievable after retire.