-
-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable AdditionalProperties:false override #2008
Labels
Comments
I've solved the same problem by creating custom function base on oasExample: rules.yaml:
oasExampleStrict.ts
It would be good to have an option in oasExample function and such rules as an optional part of base rules anyway. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User story.
As an API designer
I want to ensure my examples are correctly spelled and typed for properties that are in my API definition
So that any consumers of mocked endpoints do not get incorrect properties
Is your feature request related to a problem?
Spectral can find examples that are bad when additionalProperties is set to false but its not something we want to do when we release API definitions as its stops evolution
Describe the solution you'd like
A mode for spectral to lint the examples against the definition and to ensure no additionalProperties are present (expect it to be a additional mode)
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: