Covering our bases

This release introduces flow coverage support! The plugin underlines uncovered lines and indicates the total number of uncovered lines in the status bar.

This release adds three new options:

• omit_function_parameters: (boolean) if true, omits the function parameters when autocompleting flow-typed functions.
• show_coverage: (boolean) if true, show coverage underlines and status bar text.
• show_sublime_autocomplete_suggestions: (boolean) if true, combines the autocomplete suggestions for Flow and Sublime's default suggestions

This release sands off a few rough edges:

• Error checking and coverage are debounced, reducing extraneous CLI calls and easing CPU load.
• .sublime-projects can override FlowIDE settings with a FlowIDE key.

A thousand thanks to @davidswinegar and @STRML for these new features!

Cross-File Completions!

Completions now work across files! They always should have, but now they actually do! 😂 You'll get type hints and autocomplete for any typed imports.

A malformed CLI argument is fixed as well.

Thanks to @cristiandima for the wonderful fixes!

Async autocomplete

Autocomplete now runs asynchronously! You should see less hanging when initializing the Flow server via autocomplete.

The Package Settings menu now includes the FlowIDE settings file so you can easily override the flow binary path.

Major bug fixes!

• We now wait for the plugin to load before calling ANY Sublime APIs. If settings.get() got called too early, the plugin received None as the path of the flow binary and subsequently failed. Waiting for plugin_loaded() fixes this issue.
• Prevent empty filenames from reaching CLI.
• Close read end of pipe when flow check returns errors. This should fix any OSError: too many open files errors.
• We now erase old flow error highlights when the // @flow pragma is removed from a file.

Better PATH handling

FlowIDE previously assumed that the flow binary was in your PATH. To fit your needs, you can now change the following settings:

flow_path (string): the path to your flow binary.
use_npm_flow (boolean): if true, uses the binary from the npm flow-bin package in the node_modules of your current file's root directory. Using flow-bin's binary will slow down editing features because it is wrapped in a Node script and starts an interpreter on each run.

Initial release

v1.0.0

Update README.md