Update JSON schema for multiple types to use anyOf - #5396
Merged
Conversation
nflaig
force-pushed
the
nflaig/update-multi-type-schemas
branch
from
April 21, 2023 13:03
331f77e to
3ad6687
Compare
Contributor
Performance Report鉁旓笍 no performance regression detected Full benchmark results
|
wemeetagain
approved these changes
Apr 21, 2023
Member
|
馃帀 This PR is included in v1.8.0 馃帀 |
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.
Motivation
With update to Fastify v4 in #5369, Ajv has been upgraded to v8, meaning "type" keywords with multiple types other than "null" are now prohibited.
This change gets rid of the following warning logs
Description
Updates JSON schema for multiple types to use
anyOfas recommended in Fastify v4 migration guide.