Fix perpetual diff on some monitor JSON fields #1291
Merged
Conversation
This file contains 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
name and message are trimmed server side so we get a perpetual diff if those fields start or end with spaces. This fixes it by tweaking the state function. Closes #1289
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jirikuncar
approved these changes
Nov 30, 2021
NouemanKHAL
approved these changes
Nov 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
name and message are trimmed server side so we get a perpetual diff if
those fields start or end with spaces. This fixes it by tweaking the
state function.
Closes #1289