Lint: sort maintainers
See original GitHub issueYes:
extra:
recipe-maintainers:
- a
- b
- c
No:
extra:
recipe-maintainers:
- a
- c
- b
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
sort-keys - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >lydell/eslint-plugin-simple-import-sort - GitHub
Sorting is the easy part of this plugin. Handling whitespace and comments is the hard part. The autofix might end up with a...
Read more >eslint-plugin-sort-annotation - NPM Package Overview - Socket
Lint rule to autofix unsorted object's keys or array. Version: 1.0.5 was published by ronpark. Start using Socket to analyze eslint-plugin-sort-annotation ...
Read more >ESLint sort imports - remarkablemark
Reminder: Don't forget to remove or disable the sort-imports rule. When you run eslint . --fix : npm run lint:fix
Read more >eslint-plugin-typescript-sort-keys - npm package - Snyk
Learn more about eslint-plugin-typescript-sort-keys: package health score, popularity, security, maintenance, versions and more.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Always GitHub handles. I mentioned (and ended up mixing) the old way of listing maintainers e-mails in spec files (RPMs), where the main maintainer being on top was important, just to make a point that I don’t think it is too important here.
Github handles. They are what goes into managing the conda-forge teams.