types(ThreadOnlyChannel): remove incorrect messages property
#10708
+12
−0
Conversation
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
Co-authored-by: TÆMBØ <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
almeidx
approved these changes
Jan 16, 2025
Jiralite
force-pushed
the
types/remove-incorrect-messages-property
branch
from
d0259b9 to
c3449b1
Compare
Jiralite
approved these changes
Jan 18, 2025
vladfrangu
approved these changes
Jan 18, 2025
Jiralite
added a commit
that referenced
this pull request
Jan 18, 2025
* types(ThreadOnlyChannel): remove incorrect `messages` property Co-authored-by: TÆMBØ <[email protected]> * test: t e s t s * test: revamp tests --------- Co-authored-by: TÆMBØ <[email protected]> Co-authored-by: Jiralite <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please describe the changes this PR makes and why it should be merged:
Resolves #10609
Status and versioning classification: