fix: Replace non-standard enumNames
with standard oneOf
in EnumSchema
#844
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.
enumNames
is not standard. It's use is keeping this project from updating toajv
v8, which keeps this library from running in some JS runtimes (example #689 ).Motivation and Context
enumNames
is not standard. Its use is keeping this project from updating toajv
v8, which keeps this library from running in some JS runtimes (example #689 ).Note: requires this schema PR to go through first
How Has This Been Tested?
Ran
npm test
and used in local developmentBreaking Changes
Will require users to update to the standard
oneOf
where usingenumNames
.Types of changes
Checklist
Additional context