escape Markdown bullets in morse conversion/deconversion output #485
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
posimagi
changed the title
…the start of morse deconversion
posimagi
force-pushed
the
escape-morse-bullets
branch
from
c7977c5 to
0fae3eb
Compare
|
updated PR |
|
don't worry about the CI failure for the moment |
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.
Description
render morse conversion output in fixed width, and escape Markdown bullets at the start of morse deconversion
Fixes #484
Type of change
How has this been tested?
Tested string manipulation in a local Python instance. I currently have no way to test the generation of Discord embeds.
Checklist
DEVELOPING.md, if it exists)CHANGELOG.mdupdated if needed