FEATURE: Solve All button for messages grouped by pattern #105
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.
This adds a button when you view messages grouped by pattern that allows you to solve all the messages contained in the group.
This also fixes a bug where the solve button wouldn't show up for individual (un-grouped) messages unless you switched to the env tab. This bug is a recent regression from 83f1ac3 where we started deferring sending env to the client until the user switches to the env tab for performance reason.
The whole solve functionality depends on
application_version
being available in the message's env, so if env has been loaded, we show the solve button if env contains anapplication_version
attribute. However, if env hasn't been loaded, we check if Logster is provided withapplication_version
via theLogster.config.application_version
config and show the button only if it's configured (i.e. it has a value) because it's very likely that the message's env contains anapplication_version
attribute if Logster is configured with one.