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
Update key-order check to check all keys #2222
Conversation
Will update this soon - struggling to find time to debug the typing errors recently |
0d24534
to
89f4f7e
Compare
@jeefberkey Any chance you can resume work on this change? It was a nice addition to make to the linter. |
89f4f7e
to
ddb4a16
Compare
A user can set the key_order setting to one of the following options: * default - checks only the order of name and action * enhanced - checks a smaller list of possible keys * everything - checks a list containing every key
ddb4a16
to
13b74a8
Compare
@ssbarnea I picked this back up a few days ago - but my tests keep on failing for things I have not modified. Can you help me with that? Also, it seems like the eco test have changed. Didn't the results used to be checked in to git? It looks like the test still uses |
Everything seems well now - I looked for a bit for a comprehensive list of allowed keys, but never found one. Hopefully the yaml file makes it a little easier to maintain. @ssbarnea Thanks! |
A user can set the key_order setting to one of the following options: