Add support for MTProto rich messages#669
Open
jnordlund wants to merge 4 commits into
Open
Conversation
Threaded workers can post MessagePorts before createProxyWorkerURLs has populated the URL list. Cap attachment by the configured thread count so the first valid worker port is not closed prematurely.
This file contains hidden or 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
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.
Summary
message.rich_messagepayloads instead of falling back to unsupported media text.RichMessage,message.rich_message, andmessages.getRichMessage.Notes
Sending rich messages is out of scope. This PR handles receiving, rendering, summary text, and fetching full rich messages.
Fixes #664
Verification
node ./src/scripts/generate_mtproto_types.js src/./node_modules/.bin/tsc --noEmit --pretty false./node_modules/.bin/vitest run src/tests/richMessage.test.ts./node_modules/.bin/vite buildgit diff --checkhttp://localhost:8080/