Parser near validations / validation classes

[cdietrich]

we are working on improving our parsing and validation infrastructure.
as we are also working on a light cli which just works on a single file
we cannot run all validations in the light cli mode as not all cross references can be resolved in this mode.

we have a number of semantic validations that are very close to the parser (e.g. using deprecated keywords)
i wonder if there is an option to move these validations out of the validation phase and more close to the parsing phase.

do you have any hints where we can start investigating?

[msujew]

Hey @cdietrich,

I'm wondering whether you would need the document builder at all for that. You could probably get away with just creating the document via LangiumDocumentFactory#fromString and run the existing DocumentValidator with a custom ValidationRegistry (i.e. with those specific parser-only validations) against it. That would probably be enough. Since the document hasn't gone through the linking phase, the document validator will not even return diagnostics about unresolved references.

[cdietrich]

hmmm will try. we also are working on a solution for lokal vs non local linking errors ...

[cdietrich]

the downside of doing it in the validation registry is more or less the categorisation and not accidentially categorize wrong.
we are also looking this by having a special linker mode in vscode that makes sure validation does not traverse.