Adjust messaging of compatibility mode#766
Merged
KirillOsenkov merged 1 commit intoKirillOsenkov:mainfrom Mar 22, 2024
Merged
Conversation
KirillOsenkov
approved these changes
Mar 22, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
Adjusting the messaging, and its perceived severity, when compatibility mode kicks in.
In reality - skipping new event types/ properties - isn't realy an error, just a case of missing visualisation of some newly added diagnostic info.
This is just proposal - any alternative visualisation or wording suggestions are very welcome. I'm not very creative :-)
Proposed UX
FYI @ladipro, @rokonec