Skip to content
This repository has been archived by the owner on Oct 10, 2024. It is now read-only.

fix: use type from the reply nested content directly #21

Merged
merged 2 commits into from
Sep 8, 2023

Conversation

dmccartney
Copy link
Collaborator

This gets the nested type of a reply from the deserialized EncodedContent instead of inspecting the parameter map.

See also
xmtp/xmtp-ios#143
xmtp/xmtp-android#104

This is all part of
xmtp/xmtp-react-native#81

@dmccartney dmccartney requested review from rygine, nplasterer and a team August 5, 2023 03:24
@changeset-bot
Copy link

changeset-bot bot commented Aug 5, 2023

🦋 Changeset detected

Latest commit: ae4fcda

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@xmtp/content-type-reply Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

@neekolas neekolas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a nice improvement. Why store the type twice, when it's already present in the encoded content? Love it

@rygine
Copy link
Collaborator

rygine commented Aug 21, 2023

we also need to add a changeset to this PR so that the changes are published to NPM. there's a link above in the comment by changeset-bot that should help.

@daria-github daria-github merged commit 3ad0b8b into main Sep 8, 2023
7 checks passed
@daria-github daria-github deleted the daniel-reply-nested-type branch September 8, 2023 22:33
@github-actions github-actions bot mentioned this pull request Sep 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants