Skip to content
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 meta.type to rules #33

Merged
merged 2 commits into from
Nov 10, 2020
Merged

- Add meta.type to rules #33

merged 2 commits into from
Nov 10, 2020

Conversation

brettz9
Copy link
Contributor

@brettz9 brettz9 commented Apr 11, 2020

What is the purpose of this pull request? (put an "X" next to item)

[x] Documentation update
[ ] Bug fix
[ ] New feature
[x] Other, please explain: Add standard metadata.

What changes did you make? (Give an overview)

  • Add meta.type to rules ("layout" for all rules but no-callback-literal which is set to "suggestion")
  • Adhere to standard linting on README example
  • Add .editorconfig to prep. IDEs for proper indentation before lint checking/fixing

Which issue (if any) does this pull request address?

N/A

Is there anything you'd like reviewers to focus on?

While meta.type is normally used with eslint --fix-type (and you currently have no fixers), as official meta-data exposed to formatters, I am planning to use it in my badge formatter (which I expect to release soon; Update: now available at https://github.com/brettz9/eslint-formatter-badger ); it can show a summary of linting problems by type, e.g., "layout", "problem", or "suggestion". Regardless of how it may end up being used, it shouldn't hurt to clarify the intent of the rule by expressing meta.type.

…iteral` which is set to "suggestion")

- Adhere to standard linting on README example
- Add `.editorconfig` to prep. IDEs for proper indentation before lint checking/fixing
@brettz9
Copy link
Contributor Author

brettz9 commented May 23, 2020

Bump..

@brettz9
Copy link
Contributor Author

brettz9 commented Jul 23, 2020

Any chance you can take a look? I don't think this change should be very controversial...

Copy link
Member

@feross feross left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@feross feross merged commit bc9eb5c into standard:master Nov 10, 2020
@brettz9
Copy link
Contributor Author

brettz9 commented Nov 10, 2020

Thank you. FWIW, the tool I mentioned is functional: https://github.com/brettz9/eslint-formatter-badger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants