Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Apply same ESLint rules to TypeScript files as well
See original GitHub issueCurrently our ESLint config for JavaScript (Flow) and TypeScript are strictly separated, but when we start adding TypeScript files at some point in the future, we want to have the same ESLint support as we did for Flow files. We should extract the common parts of the configuration and eslintJS.js and eslintTS.js should strictly contain config related to Flow and TypeScript respectively, while everything else should be in eslintCommon.js that both would extend.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That’s true, it’s kinda standalone currently, but try applying to it everything that isn’t specifically Flow-related so we see what happens. When we start adding TypeScript files at some point in the future, we want to have the same ESLint support as we did for Flow files.
Of course, assign this to me 👍