Version Packages - #82
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
fiber@0.14.6
Patch Changes
#81
a7def54Thanks @MathiasWP! - Readconstwhen building a body from a schema.OpenAPI 3.1 uses JSON Schema 2020-12, where a literal is written as
constand a literal union asanyOf: [{const: "once"}, {const: "always"}]. That is what 3.1 generators emit where 3.0 would have written anenum. Fiber readexample,defaultandenum, but notconst— so it walked into the first branch, found nothing to go on, and printed thestringplaceholder for a field whose only legal values were named right there. Sending that body back got it rejected by the very document it came from.One real spec this was found against writes 543
consts and not a singleenum, so the existingenumhandling never fired once across 658 paths. Aconstis now taken as the value it names, in request skeletons and in form fields alike.