I have checked the branches or the maintainers' PRs for upcoming features.
Feature Request
When you use MarkdownSanitized.escape(String) on a text that only contains a single icon used in markdown does MarkdownSanitizer not escape it, causing weird Markdown formatting to happen.
For example:
Assume we have a user with the name _ User
When I would have the message Andre_601 is giving _ User _1 Reputation Point_ and want the MarkdownSanitizer to escape the username, will it not do that as it doesn't find two _ to escape.
This causes the above message to be displayed like this:
When in actuality it should be displayed like this:
Having an option to escape every character used for markdown, even when it's a single one, would be a useful thing as you may want to escape those characters in usernames or similar, while still having markdown formatting used.
My idea would be a boolean option that when set to true, would escape every _, *, ~, >, etc.
Example Use-Case
Use-case has explained above.
The text was updated successfully, but these errors were encountered:
General Troubleshooting
Feature Request
When you use
MarkdownSanitized.escape(String)on a text that only contains a single icon used in markdown does MarkdownSanitizer not escape it, causing weird Markdown formatting to happen.For example:
Assume we have a user with the name
_ UserWhen I would have the message
Andre_601 is giving _ User _1 Reputation Point_and want the MarkdownSanitizer to escape the username, will it not do that as it doesn't find two _ to escape.This causes the above message to be displayed like this:

When in actuality it should be displayed like this:

Having an option to escape every character used for markdown, even when it's a single one, would be a useful thing as you may want to escape those characters in usernames or similar, while still having markdown formatting used.
My idea would be a boolean option that when set to true, would escape every _, *, ~, >, etc.
Example Use-Case
Use-case has explained above.
The text was updated successfully, but these errors were encountered: