refactor: leverage OpenApiSpex.Schema.example/1 when possible
#6
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
fabiopellegrini
force-pushed
the
refactor/legerage-open-api-spex-examples
branch
from
3eedbc4 to
a5e6a7b
Compare
silvadanilo
approved these changes
Apr 11, 2025
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.
I discovered that
OpenApiSpexhas aexamplefunction for generating meaningful examples for schemas.It turns out the impelmentation is not so good, so I cannot use it for enums, arrays and numbers, but I think it makes sense to use it when possible.
I also deprecated some functions that I don't think are useful anymore as the options they implement are already inferred from schema, but if you prefer we can keep them for retro-compatibility 👍