Make it work on the fly about eslint-plugin-flowtype-errors HOT 5 CLOSED

@nmn Fixed this in a alpha version. I would really appreciate if you could test this out yourself and see if it address all the issues you have experienced:

npm i -D [email protected]

from eslint-plugin-flowtype-errors.

See this note for the reason of the design decision.

Adding that feature is actually much harder than it seems and than it needs to be. ESLint's plugin API doesn't support.

Using flow check-contents you can pass...

Yup! I've actually used flow check-contents initially but there were issues with it. If I remember correctly, it was that flow check-contents would not return file paths, which are required for the plugin to work or it could have been that it would run on a file even if it didn't have the @flow pragma (Don't quote me on this).

The biggest drawback of this plugin is how you can't get errors before saving. I'll be working on getting this ASAP.

from eslint-plugin-flowtype-errors.

@nmn After looking into this, it seems like this has to do with the way that atom runs ESLint and its plugins. On some editors, you don't need to save for eslint to report errors. Check out this issue for more on that.

I'll contact the atom-linter/linter-eslint maintainers to see how I can resolve this.

from eslint-plugin-flowtype-errors.

@nmn Seems like it depends on your editor linter plugin.

A few people seem to have this working:
#8 (comment)
#8 (comment)

What editor and plugins are you using to integrate ESLint with your editor?

from eslint-plugin-flowtype-errors.

Sorry for the late follow up. 1.4.0 has been release. I would recommend using that instead. Also are you experiencing any issues with the module anymore? If not, maybe this should be closed?

from eslint-plugin-flowtype-errors.