Linter: Signals with one or more `_` at the start are considered not as snake_case

[gikari]

If signal has one or more _ at the start, the linter complains, that is is not a snake case. I think, that it is not correct, the leading _ can be used to hide signal, or mark them as private ones.

[fstxz]

Looking at the expected linter output for signal names, this is intentional:

GDScript-formatter/tests/lint/expected/signal_name.txt

Line 2 in 46c43b0

tests/lint/input/signal_name.gd:10:signal-name:error: Signal name '_bad_signal' should be in snake_case format

I don't know why, I would have expected it to follow the same rules as variable and function names, which do allow _ at the start.

[NathanLovato]

We probably never really considered pseudo-private signals! But it's more generally a case of as I do this in my free time, I don't really have the time and mindspace to give everything the amount of thought and care it would need. Or rather, this is done collectively over time.

(thanks for the bug report!)

[fstxz]

@NathanLovato I can open a PR if you haven't started working on this yet.

[NathanLovato]

Absolutely, any PR on the linter is most welcome! And on anything actually, just the linter tends to work in more isolated units so it's a bit easier to contribute to.