Import workspace as Dependency #1856
Unanswered
kapishsingla
asked this question in
Q&A
Replies: 1 comment
-
Hi @kapishsingla, I think that by default all dsl files from the workspace are built and you can have cross references between them. You can override the DefaultScopeProvider:getGlobalScope by providing a list of visible URI is you want to restrict visibility on some files. In this case you have to implement your own logic to retrieve the visible URIs from a given document. edit: There is no concept of project in VSCode. If you want this concept you have to implement your own logic in a separate DSL or in a configuration file. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Team,
I am trying to import a workspace containing my Langium-based DSL documents (demo.lang) from project_A as a dependency into my current project_B. My expectation is that when project_B is loaded, it should automatically build project_A as part of the process.
From what I understand, I can use the
WorkspaceManager.initializeWorkspace()
method and provide the paths for both project_A and project_B while loading project_B.To provide a clearer analogy, this process is similar to importing a Maven project in the
pom.xml
file, allowing us to use the classes from the imported project.Could you please guide me on how to proceed with this implementation? Additionally, is my understanding of how to load and integrate different projects correct?
Beta Was this translation helpful? Give feedback.
All reactions