Decorating Expense 'id' with 'int64' in the OpenAPI spec#69
Merged
jas14 merged 1 commit intosplitwise:mainfrom Jan 28, 2023
edblankenship:main
Merged
Decorating Expense 'id' with 'int64' in the OpenAPI spec#69jas14 merged 1 commit intosplitwise:mainfrom edblankenship:main
jas14 merged 1 commit intosplitwise:mainfrom
edblankenship:main
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
2 participants
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.
Hi 👋
Wanted to offer a contribution to the OpenAPI spec after noticing a recent
expensebeing returned with anidvalue greater than what anint32can hold. Added aformatdecoration to indicate to OpenAPI code generators that they should store this field as anint64orlongdepending on the language.📑 OpenAPI data model specification for Numbers
Thanks and let me know if you have any feedback on the contribution 🙏