-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
json deserialization for legacy reactions #1488
Open
cameronvoell
wants to merge
11
commits into
main
Choose a base branch
from
cv/01-10-json_deserialization_for_legacy_reactions
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+76
−8
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
76983ce
json deserialization for legacy reactions
cameronvoell 63609c5
Merge branch 'main' into cv/01-10-json_deserialization_for_legacy_rea…
cameronvoell 1744eca
clarify log message when messages not sent as encoded content
cameronvoell a50227c
move legacy reaction json deserialization to content-types crate
cameronvoell 6be91c6
Merge branch 'main' into cv/01-10-json_deserialization_for_legacy_rea…
cameronvoell 62248ee
Merge branch 'main' into cv/01-10-json_deserialization_for_legacy_rea…
cameronvoell baddd8e
Merge branch 'main' into cv/01-10-json_deserialization_for_legacy_rea…
cameronvoell 7d26913
Merge branch 'main' into cv/01-10-json_deserialization_for_legacy_rea…
cameronvoell aaa58c2
clean up naming
cameronvoell fd35630
Merge branch 'main' into cv/01-10-json_deserialization_for_legacy_rea…
cameronvoell 4ca67fe
added commit about json legacy reaction source
cameronvoell File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can't shoe-horn the legacy reaction into the new reaction type? I thought the data was about the same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Original type had arbitrary String for reaction action and reaction schema (js sdk used union type to restrict it), I updated to enum in the new proto type to be more precise so we wouldnt need to do this type of conversion across all the SDKs: https://github.com/xmtp/xmtp-android/blob/51c7b170d53f73d32d3a1d33b0d170d156183e43/library/src/main/java/org/xmtp/android/library/codecs/ReactionCodec.kt#L40-L55
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh. Too bad.
Agree the new format is nicer.