`checkGrammarTypeInfer` validation ignores declared types in other .langium files
See original GitHub issueDefinition of a rule X
and a type XType
in different files, gives you a validation error The type 'XType' is not explicitly declared and must be inferred.
interface XType {
a: string
}
X returns XType:
a=ID;
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Issues · langium/langium - GitHub
Consider existing declared interfaces when infering types types Types related issue validation Validation related issue. #844 opened ; Define an API evolution ...
Read more >ts-node ignores d.ts files while tsc successfully compiles the ...
ts files I created (while tsc has no problem with it). Project structure is: / conf/ dist/ src/ types/ package.json tsconfig.json.
Read more >Quickly create DSLs with Langium - Strumenta
A tutorial and introduction to Langium, the new language engineering tool to quickly create DSLs by TypeFox, the creators of Xtext and Theia....
Read more >Shapes Constraint Language (SHACL) - W3C
This document defines the SHACL Shapes Constraint Language, a language for validating RDF graphs against a set of conditions.
Read more >Xtext to Langium – TypeFox Blog
The grammar declaration language used in Langium is similar to Xtext but not exactly the same. This blogpost is intended for those who...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@spoenemann The unresolved return type check you added works as expected and there is no other much better place where to put it.
So I would propose to close this issue. We can create a new one if the problem described here occurs also after the type system refactoring.
@pluralia I can’t reproduce this issue using the example you provided. Could you add a real world example that produces the error mentioned above?