Repository navigation
Add unreviewed demo services with and without invoices - #8
Merged
Merged
Conversation
Contributor
Author
|
Deployed merged commit
The Railway service domain had changed to mello402.up.railway.app. |
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.
The demo catalog now has two additional independent service entries: C supports a Demo invoice and D does not. Both start without a Mello verification record, completing the four invoice/certification combinations alongside the existing reviewed A/B entries.
C is fulfilled by the existing Seller B endpoint and D by Seller A, using their current quotes and seller identities. Service display names distinguish the entries while the UI identifies the actual provider. Bazaar still matches the complete endpoint/payment terms, and verification remains specific to each service ID.
The API pre-deploy step registers missing C/D records and audit events idempotently, preserving existing services, reviews, policy and purchase history. The additive
20260906010000_service_display_namemigration runs before API startup; Web then displays names in the survey, policy list and purchase records.Validation: 394 API unit tests, 9 frontend tests and 58 focused database integration tests passed locally, with API type checking and repository lint. Integration coverage includes concurrent registration, preserving later edits/reviews, rollback on an ID conflict, independent certification gating and a complete mock purchase/invoice for a named unreviewed option.