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

jprouse/US153861-double-spaces-rule #60

Merged
merged 3 commits into from
Jul 6, 2023

Conversation

JakeProuse
Copy link
Contributor

@JakeProuse JakeProuse commented Jul 6, 2023

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 😄

@JakeProuse JakeProuse changed the title US153861 - add rule jprouse/US153861-double-spaces-rule Jul 6, 2023
Copy link
Contributor

@AntonBazhal AntonBazhal left a 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

browser-config.js Outdated Show resolved Hide resolved
@dlockhart
Copy link
Member

This makes sense to me, although should it maybe go in common-config.js? We likely want it in both browser-based JS and Node.js.

@JakeProuse
Copy link
Contributor Author

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?

@dlockhart
Copy link
Member

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 0.x like this library is, minor version bumps are actually treated as major. So ^0.1 won't automatically install 0.2 vs. ^1 would install 1.1, 1.2, etc.

@JakeProuse
Copy link
Contributor Author

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 0.x like this library is, minor version bumps are actually treated as major. So ^0.1 won't automatically install 0.2 vs. ^1 would install 1.1, 1.2, etc.

Ah so if this PR gets merged I should add feat: in the commit message so we get a minor / pseudo-major version bump?

@dlockhart
Copy link
Member

Exactly, yeah.

@dlockhart dlockhart marked this pull request as ready for review July 6, 2023 18:38
@dlockhart dlockhart requested a review from a team as a code owner July 6, 2023 18:38
@JakeProuse
Copy link
Contributor Author

@dlockhart Is this good to merge? Wasn't sure how many checks we wanted!

@dlockhart
Copy link
Member

Yep, go for it! Squash-merge with feat: <description> in the merge commit.

@JakeProuse JakeProuse merged commit 79751ff into main Jul 6, 2023
@JakeProuse JakeProuse deleted the jprouse/US153861-double-spaces-rule branch July 6, 2023 19:09
@ghost
Copy link

ghost commented Jul 6, 2023

🎉 This PR is included in version 0.24.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@ghost ghost added the released label Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants