API add filter by reason and resolution status #1344
Conversation
This file contains 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
richrace
commented
Mar 7, 2025
packages/api/src/services/gateways/dataStoreGateways/postgres/cases/fetchCases.ts
Outdated
Show resolved
Hide resolved
richrace
commented
Mar 7, 2025
packages/api/src/services/gateways/dataStoreGateways/postgres/cases/fetchCases.ts
Outdated
Show resolved
Hide resolved
richrace
force-pushed
the
BICAWS7-3372-api-add-filter-by-reason-and-resultion-status
branch
from
b5afb4d to
6b0012d
Compare
|
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.
This "filter" was a bit more complex than the first impression
Resolved = 2andUnresolved = 1Tested SQL against prod and it is quick for general use.
It is not quick when: