refactor: [IOBP-000] Aligned biz event tag and data#574
Open
LeleDallas wants to merge 6 commits intomasterfrom
Open
refactor: [IOBP-000] Aligned biz event tag and data#574LeleDallas wants to merge 6 commits intomasterfrom
LeleDallas wants to merge 6 commits intomasterfrom
Conversation
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.
Short description
This pull request introduces enhancements and refactoring to the payments notices feature, focusing on improved test data generation, more flexible configuration for receipt endpoints, and updates to API model references
List of changes proposed in this pull request
notices.tsto use an array foruserNoticesinstead of aMap, simplifying add/remove operations and enabling easier ordering and shuffling of test datashuffleNoticesfunction to randomize the order of notices at startupreceiptsconfiguration section toIoDevServerConfig, allowing the/paids/:eventId/pdfendpoint to return a customizable 404 response (with a structured error object) if configured, instead of the default file or error/paids/:eventId/pdfroute to use the newpdfNotFoundResponseconfig value if present, and improved default error handling for missing attachmentsHow to test
Verify receipt and cart receipt visibility in app