lint: Allow signal names that start with _ to be considered as snake_case - #356
Merged
Merged
Conversation
fstxz
changed the title
_ to be snake_case_ to be considered as snake_case
fstxz
force-pushed
the
private_signal
branch
from
September 14, 2026 17:30
1404812 to
d1955c9
Compare
This comment has been minimized.
This comment has been minimized.
fstxz
force-pushed
the
private_signal
branch
from
September 14, 2026 18:28
d1955c9 to
67d03dd
Compare
Contributor
Author
|
Thanks, should be fixed now. |
fstxz
force-pushed
the
private_signal
branch
from
September 15, 2026 06:47
7343bdb to
88df310
Compare
Contributor
|
Thank you very much for taking the time to help! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
_at the start are considered not as snake_case #355