Skip to content

chore: allow commonly used underscore-dangle exceptions#19

Open
davidding wants to merge 3 commits intomainfrom
feature/no-underscore-dangle-exceptions
Open

chore: allow commonly used underscore-dangle exceptions#19
davidding wants to merge 3 commits intomainfrom
feature/no-underscore-dangle-exceptions

Conversation

@davidding
Copy link
Copy Markdown

No description provided.

denisolvr
denisolvr previously approved these changes Nov 27, 2025
darkmavis1980
darkmavis1980 previously approved these changes Nov 27, 2025
@darkmavis1980
Copy link
Copy Markdown
Contributor

@davidding just bear in mind that this will be only available in version 3.0.0 which is still in beta

darkmavis1980
darkmavis1980 previously approved these changes Nov 27, 2025
@darkmavis1980
Copy link
Copy Markdown
Contributor

Also can you set the version as we don't have Jenkins doing it for us here?
npm version prerelease and then git push origin --tags

denisolvr
denisolvr previously approved these changes Feb 23, 2026
David Ding and others added 2 commits March 10, 2026 08:07
@davidding davidding force-pushed the feature/no-underscore-dangle-exceptions branch from dbd8540 to 7b4c426 Compare March 10, 2026 08:07
@davidding davidding dismissed stale reviews from darkmavis1980 and denisolvr via 8310197 March 10, 2026 08:08
{
"name": "@hs-web-team/eslint-config-node",
"version": "3.2.0",
"version": "3.2.1-0",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Something wrong here

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can you just please add a preid of next

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Also, unless you want to test and iterate the changes to see if they work, you should just set the version directly, so this should be just 3.2.1

Copy link
Copy Markdown
Contributor

@darkmavis1980 darkmavis1980 left a comment

Choose a reason for hiding this comment

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

Version is very wrong

@davidding
Copy link
Copy Markdown
Author

Version is very wrong

@darkmavis1980 - How so? It is completely valid semver - https://semver.org/#spec-item-9

You had said:

Also can you set the version as we don't have Jenkins doing it for us here?
npm version prerelease and then git push origin --tags

That's what I did:

npm-version-prerelease

We don't have a preid set in the project. The default is the empty string (which, of course, results in valid version numbers).

If we want to add a preid, we can do that - but there is nothing "very wrong" with 3.2.1-0 as a version 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants