[FEATURE] Imports from Anywhere on the FS

[georg-schwarz]

User Story

1. As a {Jayvee user}
2. I want {to perform Imports from anywhere of my file system}
3. So that {model parsing and interpretation don't depend on the current directory (like in Python)}

User Acceptance Criteria

• Imported documents are dynamically added to the LSP instead of being restricted to a fixed working directory.

See discussion in #590 for more details.

Definitions of Done

• A PR has been opened and accepted
• All user acceptance criteria are met
• All tests are passing

[georg-schwarz]

Gave it a try to dynamically load files when imported on this branch: https://github.com/jvalue/jayvee/compare/dynamically-load-imported-documents?expand=1

Ran into a roadblock because Langium's ScopeProvider has a synchronous interface. I will open a ticket (eclipse-langium/langium#1554) to determine whether they would be able to make that async in future releases.

[georg-schwarz]

Was pointed to this discussion: eclipse-langium/langium#1308
We should be able to implement it in that way I think.

[rhazn]

FYI, with Jayvee 0.6.0, importing documents above a model still shows an error in the VSCode extension, e.g. consider the following directories:

a/model.jv
b/shared.jv

If you open model.jv in VSCode, it will show the Import from "./../b/shared.jv" could be resolved. Check if the file exists in the given location.

use {
	Something,
} from "./../b/shared.jv";

If you run model.jv from a, it errors. If you run a/model.jv from the root dir, it works. Not sure if I should create a new bug for this or if it is part of this PR @georg-schwarz ?

[rhazn]

Actually, the language server part of this might have been a caching (?) issue on my side, seems to work now and not show an error in the jv model. However, the interpreter still errors if run from a.

[georg-schwarz]

Yes, the interpreter and the VSCode plugin take the current directory (where jv is run / the IDE is opened) as basis to load files. That means we cannot link to anything outside of that scope yet.

Quick-fix for now: Start the editor or execute the jv program from a higher directory.

For implementing a more dynamic loading we will have to rework the whole file loading mechanism. Caveat: Auto-complete will never work in that regard.