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
There's a few quality-of-life issues with errors and warnings.
Warnings are only printed once, so if the module isn't changed warnings won't be shown again. We could save warnings and print them out on each reload.
We already parse compilation output, so this should be fairly easy to fix.
Note: If a file is compiled, then an error is introduced, and then the file is reverted back to its original form, it will be reloaded but no [n of m] Compiling ModuleName message will be printed; this means that we need some more sophisticated logic than just looking at compilation messages to determine when to clear diagnostics for a file.
There's a few quality-of-life issues with errors and warnings.
Warnings are only printed once, so if the module isn't changed warnings won't be shown again. We could save warnings and print them out on each reload.
Similarly, errors can get buried under compilation output, so it could be useful to replay those as well.
We already parse compilation output, so this should be fairly easy to fix.
Note: If a file is compiled, then an error is introduced, and then the file is reverted back to its original form, it will be reloaded but no
[n of m] Compiling ModuleName
message will be printed; this means that we need some more sophisticated logic than just looking at compilation messages to determine when to clear diagnostics for a file.From SyncLinear.com | DUX-1511
The text was updated successfully, but these errors were encountered: