feat: do not store channelData in thread state #1337
Merged
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.
Cleaning up types a bit:
Thread
is initialized without an underlyingChannel
is not very useful. Now threads always have a channel.channelData
separately is excessive, we have it inchannel
.staggeredRead
removed for now, it's supposed to make a triumphant return at some point.This will break ThreadProvider in React SDK, fixed in a follow-up PR.