`negated` rule API

[abitrolly]

I am trying add the new rule to fix #3810 and I find the lines around negated puzzling. For example,

commitlint/@commitlint/rules/src/body-case.ts

Line 5 in 3ee4c28

const negated = (when?: string) => when === 'never';

Why each rule has to calculate this negated property?
Why it can not just receive the negated as a bool param?
Where this negated is realistically used?

[escapedcat]

Sorry, can't really answer this question

[abitrolly]

If you can't answer, then I have no chance to understand it too. :D

[knocte]

IMO, if the when param always has values 'always' or 'never' in commitlint's codebase, then, yes, we should refactor to make it a bool. Maybe we should check git-blame to see who coded this in the first place and ask her/him why did he choose a string? Maybe she/he was envisioning more things besides 'always', 'never', ...? (I wonder how a 'sometimes' could work.)