4 ms·
One danger of having a bunch of custom eslint rules is that you may be papering over weak abstractions in your codebase. Sometimes it's a problem with lack of m
by bjterry 9y ago
One danger of having a bunch of custom eslint rules is that you may be papering over weak abstractions in your codebase. Sometimes it's a problem with lack of macros (or a powerful type system) but other times rethinking the way you are using libraries can be a bigger win for maintainability.
- dmnd 9y agoRight on. Flexport definitely has few custom rules that address things that would be better solved by nicer abstractions. One great thing about lint rules though is that it's usually pretty easy to apply them to all existing code. That means you get the benefit of finding problems in older code without having to refactor into better abstractions or types. Also: hi, BJ :)