We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Langium version: 3.3.0 Package name: langium
.waitUntil
The current check requires that the document be in a more advanced state than the requested state:
langium/packages/langium/src/workspace/document-builder.ts
Lines 423 to 428 in c3afb24
On the other hand, the fallback check for the workspace only requires the same or more advanced state:
Lines 429 to 433 in c3afb24
Link to code example:
waitUntil never resolves (unless the document is rebuilt later) if the document is available in the target state.
waitUntil
waitUntil should resolve immediately if the document is already available in the desired state. Or at least that's what I think I'd expect.
The text was updated successfully, but these errors were encountered:
Ah, damn. That was supposed to be a >=. I'll submit a fix for that tomorrow :)
>=
Sorry, something went wrong.
That was supposed to be a >=.
Thought so, but I just started working with Langium, so I didn't want to assume there was a reason I couldn't divine. :-)
No branches or pull requests
Langium version: 3.3.0
Package name: langium
Steps To Reproduce
.waitUntil
with the desired state.The current check requires that the document be in a more advanced state than the requested state:
langium/packages/langium/src/workspace/document-builder.ts
Lines 423 to 428 in c3afb24
On the other hand, the fallback check for the workspace only requires the same or more advanced state:
langium/packages/langium/src/workspace/document-builder.ts
Lines 429 to 433 in c3afb24
Link to code example:
The current behavior
waitUntil
never resolves (unless the document is rebuilt later) if the document is available in the target state.The expected behavior
waitUntil
should resolve immediately if the document is already available in the desired state. Or at least that's what I think I'd expect.The text was updated successfully, but these errors were encountered: