Repository navigation
cms: the inbox in pages of 50, one statement query, Proposal indexes, photo rollback - #28
Merged
Merged
Conversation
…xes, and a photo update that rolls back
|
review: a737707 |
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 LTET-18
Changed
?page=nbesidekindandstatus). A bad or out-of-range page is a 404 "Page not found", as on the runs list. The kind chips count across every page.id IN (...)query, without their history, and skips the query when a page has no disputes.&page=nwhen the proposal sits past the first page.Proposal.runIdandProposal.statementId(indexes only, no data change).Tested
npm run build,npm run test:unit,npm run test:e2e,npx prettier --check .pass on the head.Look at first
src/services/content-service.tsupdateContender: the order of read, write, update and rollback.prisma/migrations/20261107000300_proposal_indexes.