New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for flow syntax extensions. #592
Comments
You can, just use the |
So I run into following issue gajus/eslint-plugin-flowtype#72 when using standard with |
Also babel/babel-eslint#293 seems relevant here. |
@Gozala Are you specifying the flowtype plugin in your {
"standard": {
"plugins": ["flowtype"]
}
} Setting a custom parser and plugins are the only ways you can try to solve this issue with If you require enabling extra rules from the flowtype plugin and/or disabling rules in |
@feross Yeap that is pretty much what I use: {
"standard": {
"parser": "babel-eslint",
"plugins": [
"flowtype"
]
} The problem as described in babel/babel-eslint#293 is that babel-eslint does not seem to have a way of informing eslint that type import is different from value import & there for eslint will report duplicate imports.
That is what I end up doing for now, but I would much rather not do that. Maybe standard could avoid this issue by using import/no-duplicates instead of stock no-duplicates ? |
The import plugin actually looks really well done. Adding another eslint plugin is not ideal for running time, but if there are other rules in there that would make |
@feross I believe it primary selling point is:
Also should I open new issue regarding duplicate imports issue caused by |
Would not it be reasonably to allow configuring those plugins ? It would not solve the duplicate imports issue I'm afraid, but I did also notice that I'm unable to configure |
Created a separate issue in regards to |
This is a slippery slope. When you see If you really want a flow-type variant of |
Thanks. I have followed this advice and created https://github.com/Gozala/standard-flow and https://github.com/Gozala/eslint-config-standard-flow to add flow support and lint type annotations with the same rules as rest of the code. |
I think that forcing forks is terrible idea, because they almost always lags behind main library and ends up unmaintained. |
Is there way to support flow syntax extensions for projects that want to use that ?
The text was updated successfully, but these errors were encountered: