Treat window/progress messages as log messages #316
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These messages should only be displayed if
log_level
is set to'Log'
.Back in #130 support was added for
window/progress
messages which are sent byrls
. However, these messages are a bit incessant and quickly get very annoying, and as it is now there is no way to disable them. This PR treats these messages as "Log" level messages and will therefore only display them iflog_level
is set to'Log'
.I don't love the hard codedEDIT: I added a new function4
in here and I am open to suggestions on a better solution, but as far as I can tell the log levels aren't enumerated anywhere so hard coding is the only possible approach (thewindow/progress
messages do not have atype
parameter like thewindow/logMessage
messages do).lsc#config#messageType
so that we can avoid using magic numbers.