[RFC] Publish and Use: Elements and Libraries #476
Conversation
| - Langium might not support this scoping mechanism out-of-the-box (more complex implementation) | ||
|
|
||
| ## Alternatives | ||
|
|
||
| - "use" syntax without braces, etc., `use MyDomainLibrary1, MyDomainLibrary2 from './path/to/file.jv';` | ||
| - "use" syntax without braces, etc., `use MyDomainPackage1, MyDomainPackage2 from './path/to/file.jv';` |
There was a problem hiding this comment.
We kind of defaulted to this (I assume from TypeScript experience) but I actually agree. Why have bracers? I would remove them.
There was a problem hiding this comment.
I really like the braces.
Without it seems like some default exports (as a TS/JS-influenced dev) or different statements (int a = 0, b = 1). Braces clarify this imo.
There was a problem hiding this comment.
From a visual perspective, I also like the braces. Without braces, I'm unsure how very long use statements would be split into separate lines.
| - Langium might not support this scoping mechanism out-of-the-box (more complex implementation) | ||
|
|
||
| ## Alternatives | ||
|
|
||
| - "use" syntax without braces, etc., `use MyDomainLibrary1, MyDomainLibrary2 from './path/to/file.jv';` | ||
| - "use" syntax without braces, etc., `use MyDomainPackage1, MyDomainPackage2 from './path/to/file.jv';` |
There was a problem hiding this comment.
I really like the braces.
Without it seems like some default exports (as a TS/JS-influenced dev) or different statements (int a = 0, b = 1). Braces clarify this imo.
|
Thanks for your reviews - I think we designed something very useful here that will bring Jayvee one step closer to a productive DSL! I incorporated the changes. Any last words before merging? |
|
No, go for it, good job writing 😅👍. |
This PR is a reissue of #474.
Introduce concepts to enable multi-file Jayvee:
publishelements of a jv file for reuse in other files of the same projectlibrariesfor bundling elements for reuse in other projectsuseof elements and libraries in other files / projects