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

resolve #867: remove k[A-Z][A-Za-z\d]*$ sub-rule from var-naming #871

Merged
merged 2 commits into from Aug 16, 2023

Conversation

martinsirbe
Copy link
Contributor

@martinsirbe martinsirbe commented Aug 16, 2023

This PR proposes the removal of k[A-Z][A-Za-z\d]*$ sub-rule from var-naming, as it doesn't clearly justify the reason for the check and fails to properly tackle any potential issues with Hungarian notation.

The emphasis is on ensuring clarity, reducing confusion, and enhancing the overall user experience for revive users.

The sub-rule originates from golang/lint and has in the past led to false positives and confusion, see golang/lint#258.

Closes #867

@martinsirbe martinsirbe force-pushed the fix/867 branch 3 times, most recently from 0000867 to 0000867 Compare August 16, 2023 10:22
@chavacava
Copy link
Collaborator

chavacava commented Aug 16, 2023

Hi @martinsirbe, thanks for the PR!
To go on with the merge, it will be necessary to update the tests of the rule to stop testing the case we are not logger supporting.

@chavacava chavacava merged commit 19a95d9 into mgechev:master Aug 16, 2023
4 checks passed
@martinsirbe martinsirbe deleted the fix/867 branch August 16, 2023 11:25
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.

var-naming: don't use leading k in Go names, vague and unclear failure description
2 participants