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
Since #115 we can use several .ale source files. However, when a validation error (not a parsing error) is detected in one file, it will always be shown as a marker in the ALE editor, even if the error doesn't originate from the edited file.
Expected behavior
The error marker is only added to the editor when the error actually comes from the edited file.
How to reproduce
Steps to reproduce the behavior:
Create a new ALE project
Add a new ALE source file (and add it to the environment)
Bug description
Since #115 we can use several .ale source files. However, when a validation error (not a parsing error) is detected in one file, it will always be shown as a marker in the ALE editor, even if the error doesn't originate from the edited file.
Expected behavior
The error marker is only added to the editor when the error actually comes from the edited file.
How to reproduce
Steps to reproduce the behavior:
self := 12;
)Additional context
Screenshot
Errors come from the left file and are reported on the right one as well:
The text was updated successfully, but these errors were encountered: