Repository navigation
chore(frontend): sync the client with the organization currency contract - #91
Merged
Merged
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
1 participant
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.
What
OC-04 of
organization-currencies, frontend side: copiesopenapi.jsonfrom apidevelopand regeneratestypes/api.tswithbun run codegen. The diff is the currency catalogue endpoints (GET /api/currencies, the superadmin/api/admin/currenciesroutes),currency_codeon the organization resource and requests, and thecurrencies.manageability. Generated, not hand-edited.Verification
bun run codegen:checkpasses;scripts/verify-openapi-parity.shreportsopenapi.jsonidentical across api, frontend and backoffice.