LSP caches local imports, responds slowly to some changes #47
Description
When functions are redefined in a local module, the LSP doesn't always refresh for that change unless the import in the file includes :fresh true. This could be made default behavior for the LSP specifically.
When a new module file is created in the local project tree, the LSP doesn't always recognize the existence of that module file. Module identification only happens during LSP startup—might be possible to insert a refresh of the module lookup only when a diagnostic error is received.
Clarification of #42 .