You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 20, 2018. It is now read-only.
It's kinda hard to keep up with all eslint features, so maybe we should just extend eslint:recommended? Then it also becomes more clear which are our overrides.
How about depending on and extending https://github.com/airbnb/javascript/tree/master/packages/eslint-config-airbnb, since they're actively maintaining it. We've already used it as a base when we started this config. We made some changes for our own needs but 95% is airbnb style. Another advantage would be that they also maintain a style guide and that their config is in line with that.
I might look into this, because we would actually need to be able to solve #6 in our current project where Purescript interop is only available through ES5, not ES6. Because the foreign function interface is also the place where the compiler can help the least and where most bugs are to be expected, a solid linter would be necessary. We also have other projects that are purely ES5 and that we will maintain for a while longer.
Is there anything I need to know with regards to trying to solve this issue? Still not sure whether tackling this is worth it, but if the problem keeps bugging me, it might be 😄
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It's kinda hard to keep up with all eslint features, so maybe we should just extend
eslint:recommended
? Then it also becomes more clear which are our overrides.Cf. https://github.com/rackt/eslint-config-rackt
The text was updated successfully, but these errors were encountered: