Klaus Meinhardt

@ahanriat why is this important to you? there is only one small bug fix that is relevant for rules in this package.

This is not possible to achieve at the moment. The rule doesn't use type information and is therefore not able to tell whether a variable has a primitive type. There...

That seems reasonable to me. I'm definitely onboard with the change to only show an error if the get accessor contains a read or the set accessor contains a write...

I agree that this is a valid use case. The blacklist would be pretty hard to implement as regular expression. Combining that with a minimum length makes it even worse....

Sorry for not answering for so long. This one totally slipped through. It's currently not possible to configure the requested behavior. Something similar exists for variables that are assigned a...

I thought about allowing underscore prefixed variables in array destructuring (similar to object destructuring). But in array destructuring you can simply omit the variable completely. That's why I decided not...

So the proposal here is to add an option to ignore all underscore-prefixed variables, parameters and destructuring bindings? IMO that sounds reasonable. If someone wants to contribute, please send a...

The rule currently doesn't check object literal properties. Typically there is a contextual type for the object literal, i.e. the variable you are assigning the object to is typed by...

I agree that this is not the ideal behavior. The rule currently tries to only remove the necessary tokens from your code. It doesn't handle formatting (or reformatting) at all....

Exported enums may be used outside of the library in a dynamic way that is not supported with const enums. That could be configured by introducing a new configuration option....