-
Notifications
You must be signed in to change notification settings - Fork 6
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
jprouse/US153861-double-spaces-rule #60
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.
I'm personally a fan of this rule
This makes sense to me, although should it maybe go in |
I know this would likely set off linters around brightspace, would this be a big enough change for a major version or do you often just make minor updates and expect repos to make updates? |
So NPM versions (really semantic versioning) has this weird thing where when you're at |
Ah so if this PR gets merged I should add |
Exactly, yeah. |
@dlockhart Is this good to merge? Wasn't sure how many checks we wanted! |
Yep, go for it! Squash-merge with |
🎉 This PR is included in version 0.24.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Rally Story: https://rally1.rallydev.com/#/?detail=/userstory/704556573471&fdp=true
Hi Gaudi, we are adding the no-multi-spaces rule to one of our repos and thought to check here and see if this is something useful for any of the existing configs (we currently use the browser-config a lot). We're aiming to avoid making custom rules in the eslint files in all our projects but no harm if this isn't desired 😄