Skip to content
This repository was archived by the owner on Jul 7, 2025. It is now read-only.

Add filter for unsupported content types without a fallback#128

Open
rygine wants to merge 2 commits intomainfrom
rygine/filter-messages
Open

Add filter for unsupported content types without a fallback#128
rygine wants to merge 2 commits intomainfrom
rygine/filter-messages

Conversation

@rygine
Copy link
Copy Markdown
Contributor

@rygine rygine commented Oct 24, 2023

in this PR:

  • added filter to useMessages hook that removes messages with unsupported content types and no fallback content
  • added disableUnsupportedNoFallbackFiltering option to useMessages hook to allow for disabling of the filter

@rygine rygine requested a review from a team October 24, 2023 17:11
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Oct 24, 2023

🦋 Changeset detected

Latest commit: 9336d24

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

This PR includes changesets to release 1 package
Name Type
@xmtp/react-sdk Minor

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

@rygine rygine requested a review from jhaaaa as a code owner October 24, 2023 17:12
Copy link
Copy Markdown
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.

I thought we were just going to handle this in the JS SDK

@rygine
Copy link
Copy Markdown
Contributor Author

rygine commented Oct 24, 2023

I thought we were just going to handle this in the JS SDK

i think the JS SDK should remain an unbiased conduit to the network. that being said, adding this filter to the JS SDK creates issues around message paging. i don't think the added complexity would be worth it.

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.

2 participants