Badisi

I was thinking about making the rule configurable like so: ```ts rules: { /** * subject-empty * condition: subject is empty * rule: always | never * value: array of...

Yeah, I questioned myself too when writing it as I'm not too familiar with how the rules are working ^^' I was reading it that way: --- > 'subject-empty': [2,...

I don't know but it was not my intention here. I just shared my interpretation of how the rule could be used. Users could use it in two ways by...

Ok got it, it's just the other way round. Thanks ;-) Do you think this is something that could be implemented ?

@escapedcat, I've had a look at the code but there seems to be no context shared between rules. I need to get the `types` (declared by the `type-enum`) in the...

@knocte, I wanted to make sure that the given types were matching the ones in `type-enum`. But you are right I can easily get rid of that and let the...

@knocte, I have submitted another PR based on our discussions. Regarding the regexp issue, are you suggesting that I fix it on my own with a custom `headerPattern` ? Fixing...

That's right ^^ I would have loved to help, but I'm just not confident enough to put my hands on a core feature, especially when this issue is around since...

Hello @knocte :) Any updates regarding this feature ? Thanks!

Still an issue in `[email protected]` (Node 20). ----- I also found (like @bweigel answer) that it's no really related to the `version` itself but to the `` argument that is...