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

Jump to bottom

no-regex-spaces should use internal rule message format #7052

Closed
platinumazure opened this issue Sep 3, 2016 · 0 comments
Closed

no-regex-spaces should use internal rule message format #7052

platinumazure opened this issue Sep 3, 2016 · 0 comments
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion chore This change is not user-facing rule Relates to ESLint's core rules

Comments

@platinumazure
Copy link
Member

Now that #7041 is merged, I can fix no-regex-spaces to use the internal message format.

PR incoming shortly.
@eslintbot eslintbot added the triage An ESLint team member will look at this issue soon label Sep 3, 2016
@platinumazure platinumazure added rule Relates to ESLint's core rules accepted There is consensus among the team that this change meets the criteria for inclusion chore This change is not user-facing and removed triage An ESLint team member will look at this issue soon labels Sep 3, 2016
platinumazure added a commit that referenced this issue Sep 3, 2016
@platinumazure
Chore: no-regex-spaces uses internal rule message format (fixes #7052)
a59db9c
@platinumazure platinumazure mentioned this issue Sep 3, 2016
Merged
@platinumazure platinumazure changed the title Chore: no-regex-spaces should use internal rule message format no-regex-spaces should use internal rule message format Sep 3, 2016
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 6, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion chore This change is not user-facing rule Relates to ESLint's core rules
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@platinumazure @eslintbot