I haven't reviewed the code yet, but
Instead of creating a special any type, I would suggest just making it an optional tuple element.
type Options = [('fields' | 'getters')?];
@c32hedge cheers, those were good catches 😅
Thinking about it some more I think I'd be happy to make
Very clever - that's much better than having a special type 😄
I'll use the optional tuple, but given the above I'm happy to set a default if you'd like 🙂
Also, the build failed due to missing
Yeah I was wondering that too.
I don't think that the rule name should include
On an aside: do you have any opinions on plural vs singular rule names? it's another one of those things I've hit a couple of times where neither seems to strongly win out vs the other to me :/
I think that as long as the name makes sense it doesn't really matter.
Examples from eyeballing our rule list: