import handling

[borovan]

Hi Ryan,

Would it be possible to have something like in VSCode for go, where the imports automatically get added/removed based on the code? What's the complexity of something like that?

It would save us so much time. Also, would help getting rid of unneeded imports which is huge when you have loads of canisters.

[borovan]

I know there was a Motoko Formatter v0.0.6 but it doesn't seem to work together with the VS Motoko plugin

[rvanasa]

For sure! This is a planned feature, and I am gradually making progress towards this in the background.

[heitor-lassarote]

Hi, we see #127 and #142 seems to have mostly resolved it, by automatically adding imports on completions for the module name (but not fields), and also quick fixes to automatically import them. Is it correct that what's needed now is to handle unused imports? Also, organize imports seem to delete imports (even used ones), so also to improve this functionality?

[rvanasa]

Also, organize imports seem to delete imports (even used ones), so also to improve this functionality?

There are currently a few bugs with the "organize imports" functionality, related to the AST being out of date with the source code when editing compile errors, iirc. It's possible that this was (partially) resolved in #334. We can remove unused imports now that the Motoko compiler includes a warning which gives the start/end location of a removable import.