MrHen

I recently had to disable `react/jsx-one-expression-per-line` because it made things like this much harder to read: ``` ABC { one && DEF } GHI {two} JKL ``` Result: ``` ABC...

I think a rule for private fields would be awesome, yeah. I don't think we can realistically auto-fix those, however, because people abuse `_foo` access too regularly and it would...

Yeah. As a general principle, I prefer rules to be have the smallest reasonable scope. In this case, I can also see why a team might want to convert to...

FYI, in case anyone else bumps into this via searching, there is a few weird gotchas when using the `type_cast()` workaround from @ryanbutterfield. ``` fd = FieldDefinition.objects.get(...) # retrieve existing...

Use something like this: ``` account_model_cls = account_model_def.model_class() accounts = account_model_cls.objects.all() ```

We just hit this issue with a very similar setup. We have KCL inside of a Docker container and during the initial container build Maven had 429 errors which prevented...

I'm **for** typing and TypeScript but I am **against** supporting gobs of different pseudo-JavaScript languages based on the whims of whatever maintainers happen to be around. Babel seems ubiquitous at...

Them I'm all for it. Viva la typing.

Personally, I've never been a big fan of using `includes` in this manner _for JavaScript_ because it causes the code to read "backwards". I want to see the variable on...

I was under the impression that `index.js` is always preferred over `Index.js` because it's a special file name. I think, at heart, there are slightly different rules being discussed. The...