Implement add-import-statement intention

Feature Proposal

Intention Action: Add Import Statement

When the cursor is over an unresolved reference which could be resolved by importing a module in the project, an intention should be provided to easily add the import.

Details

• We should look for candidate modules in the user’s source files as well as from elm-package.json. I think this is already handled by the plugin since we treat elm-stuff as a source-root.
• If the selected element is a “dotted” name (e.g. String.length), then just the module name should be imported (e.g. import String)
• If the selected element is a “bare” name (e.g. length), then the value’s name itself should be imported (e.g. import String exposing (length))

The last example, length, would presumably have many candidates. The user should be shown the list of candidate modules to select from.

Related Work

• optimize imports
• convert between importing a value name in a qualified manner (String.length) and unqualified (length)
• assuming that we extend code completion to present currently-unresolvable-references, selecting such a result would add an import in a manner similar to this intention
• add-to-exports (see #18)

[durkiewicz]

@klazuka The feature is released. I’ve also made master branch the master so you don’t need to worry about Elm 0.16 anymore.

[klazuka]

Done pending release.