fix: Telegram Bad Request: can't parse entities #1546
Merged
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
monilpat
approved these changes
Dec 28, 2024
1to3for5vi7ate9x
pushed a commit
to 1to3for5vi7ate9x/eliza
that referenced
this pull request
Jan 26, 2025
…n-issues fix: Telegram Bad Request: can't parse entities
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Relates to:
PR 1229
Risks
Low: Fixes TG message handling with markdown, introduced with PR 1229
Background
What does this PR do?
What kind of change is this?
Bug fixes (non-breaking change which fixes an issue):
Fixes TG messages "Bad Request: can't parse entities"
And still keeps markdown functionality for regular messages.
Why are we doing this? Any context or related work?
Documentation changes needed?
N/A
Testing
Where should a reviewer start?
Detailed testing steps
Added escapeMarkdown function within /utils.ts, imported to messageManager, and passing through TG messages.
Deploy Notes
N/A
Database changes
N/A
Deployment instructions
Discord username
ninja_dev