-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add linter to make sure statuses have consistent inheritance #7351
Conversation
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 looks pretty straightforward, happy to review this to completion. In this cases the changes to the data are few enough that I think it's fine to do them in the same PR as the lint.
Do you think we should also lint for experimental status, that a non-experimental feature must have a non-experimental parent?
Right, also it shouldn't be possible to have a standard feature as a child of a non-standard feature. So all 3 statuses should be possible to have similar lints for. |
Got a lot more after including |
This pull request has merge conflicts that must be resolved before we can merge this. |
This pull request has merge conflicts that must be resolved before we can merge this. |
Looks like this needs to be formatted, could you run a formatter real quick to see what needs to be done to make this linter pass? |
(#15932 exists for this) |
This pull request has merge conflicts that must be resolved before it can be merged. |
This pull request has merge conflicts that must be resolved before it can be merged. |
I don't think I'll merge repeatedly only to be replaced by others, closing. |
A checklist to help your pull request get merged faster: