Replies: 2 comments 5 replies
-
@goto40 afaik the fix is only in the final release |
Beta Was this translation helpful? Give feedback.
4 replies
-
I tried with 3.1 now: the problem persists, but I analyzed the effect further: (we are also still checking if it is an issue in our formatter) @msujew : for me it "works" now - however I could try to mimic the effect in a minimal example if you wish (or do you think it is explainable with other known issues already?) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am using langium 3.1-next (the same was observed with langium 2.x and we had no issues originating from switching to 3.1-next so far. All other tests seems to pass :-) )
We had already have some issues when specifying formatter behavior which has conflicting requirements.
Therefore we build a test to reformat a model folder multiple times (2x) and check if we get a "stable" format in the end by comparing the result of the first run with the second run...
Now, we still have some "flickering" cases.
I observed that this behavior was influence by spaces in the original model file (no space after the
,
):This produced a flickering behavior: an extra newline is inserted after the first run
However the following model resulted in a stable result (a space was added after the comma):
Now we get a stable result as expected (an no extra newline in the first run):
Is this something one could image to "disappear" the 4.x version? For us this would be ok to continue here later...
Note: probably it is not a "flickering", but a two-step process to settle down (not tested)
Beta Was this translation helpful? Give feedback.
All reactions