Open
Conversation
Used markdown-strings v2.1.3, because 3.1.x doesn't works properly.
|
Hey @butorov can you merge this? This is useful when you have certain characters in the Proxy support not sure, but escaping is needed most definitely. |
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
2 participants
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.
Added proxy support.
Reworked notify method, don't know why. Just seen it in other plugins.
Escaped markdown characters. That's important, because if you have project name with underscore character (like "backend_dev"), it will break Markdown syntax, and Telegram will return error. Used markdown-strings==2.1.3, because newer versions doesn't work properly.