Adam Lui

When a user sees a `no-missing` rule my opinion doesn't really matter, common sense is the rule is to prevent the element from being missing, which all other `no-missing` rules...

By default if fragment is not lowercase a rule called `no-missing-something` said it's missing even though it was not, IDK how this makes any sense unless a user expected this...

The option can be useful for those who want it, I'm just pointing out if they don't then they are relying on this default option so it's giving a false...

Actually this is a bug for this reason but I didn't want to re-open the other issue cuz I closed it already so i just picked change request

Wait not bug which is defined not working as intended but a flaw

Like if I made a button labeled "Close" but it opens tabs instead, but I explained it was intentional, then it is just flawed design that should still be fixed,...

Actually it's possible for someone to desire case linting and be unaware of option then this is desirable, but I'm saying the rule's prefix is literally `no-missing`, and no other...

Alternatively the name can be changed if you're adamant case should be linted by default, otherwise the user expects the rule lints for no missing fragments by default because of...

@nzakas I'm not trying to challenge you sir (just re-read your OP and realized you probably don't like me) but I use this plug-in in dozens of repos so if...

Also you made this and the other non-JS repos right after my interactions w/ 3rd-party authors of non-JS plugins + even your late AI/frontend explorations came after my interactions w...