You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Blueprint 1.37 or Theia 1.37 - 1.38, for JSON or Python files, linting does not work continuously while editing; they perform just after opening the file and stop. During editing, linters do not refresh and scan the file again; thus if there is a new error it does not show up, or if an error is corrected it stays at the editor and problems pane.
Steps to Reproduce:
Open Blueprint 1.37
Create a JSON file. Enter some random data with errors, eg. { "key1": "val1", "key2": val2_no_quotes, "key3": "val3_no_comma" "key4": "val4" }
No errors are detected. Close and reopen the file, errors will be visible.
Fix some errors, they will not disappear.
Additional Information
Operating System: Linux
Theia Version: 1.37, 1.38
This problem is not present in Blueprint 1.36.
Demo app at theia-cloud.io has the same problem for JSON and JS files. However, linter for Java files was working correctly.
The text was updated successfully, but these errors were encountered:
@msujew After downgrading msgpackr, the issue is resolved. The responsiveness of the editor was also a bit slow compared to previous versions; it also reverted back to normal after this solution.
Bug Description:
In Blueprint 1.37 or Theia 1.37 - 1.38, for JSON or Python files, linting does not work continuously while editing; they perform just after opening the file and stop. During editing, linters do not refresh and scan the file again; thus if there is a new error it does not show up, or if an error is corrected it stays at the editor and problems pane.
Steps to Reproduce:
{ "key1": "val1", "key2": val2_no_quotes, "key3": "val3_no_comma" "key4": "val4" }
Additional Information
The text was updated successfully, but these errors were encountered: