Add proper json mapping for Trigger - #677
Merged
Merged
Conversation
PierreBtz
previously approved these changes
Mar 14, 2024
PierreBtz
left a comment
PierreBtz
left a comment
Collaborator
There was a problem hiding this comment.
indeed, thanks for the fix!
Collaborator
|
Marking as breaking since a Trigger persisted with a previous version will lose those two fields when deserialised. I saw that a test is failing, I'll try to have a look. |
Contributor
Author
|
I fixed the test cases |
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.
The trigger category isn't properly handled as the JsonProperty annotation is missing for this camel case property name