-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
feat: $ref cannot have siblings #473
Conversation
078fe3e
to
2f878bc
Compare
How do you feel about not making it a rule and failing all the time same as invalid-ref does? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will probably need to be a rule if possible because JSON Schema draft 8 will allow siblings and that means OpenAPI v3.1 might allow siblings and we'll need to keep this out of spectral itself.
@philsturgeon got it, will make it a rule then. |
@philsturgeon |
c9fbc48
to
46fe6e1
Compare
Good to go! |
80650fd
to
61939f5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When that variable is renamed we are all set.
Closes #394
Checklist
Does this PR introduce a breaking change?
It's not a rule, as rules have no access to original (unresolved) data.
I don't know if it's a big deal or not, but if we do need a rule, I can make it a rule.
The code is placed in a wrong place and an extra test wouldn't hurt, so it's still a WIP.