Any character with code between 1 and 126 inclusively can be escaped anywhere with a preceding '\' character, in which case it is treated as an ordinary character and not a part of the markup. This implies that '\' character usually must be escaped with a preceding '\' character.
In the first example:
the message will be send like "ab" (the slash will disappear)
In the second example:
the message will not be sent, it will error out something like this:
Bad Request: can't parse entities: Character '(' is reserved and must be escaped with the preceding '\'
This pull request is pretty straight forward...
Telegram documentation says:
Source: https://core.telegram.org/bots/api#markdownv2-style
So here goes a simple sample program to simulate the bug:
Before the fix:
After the fix:
In the first example: the message will be send like "ab" (the slash will disappear)
In the second example: the message will not be sent, it will error out something like this:
Bad Request: can't parse entities: Character '(' is reserved and must be escaped with the preceding '\'
It's a small fix, but an important one.
[]'s