Compatibility with other customizable markdown standards #28
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
added 2 commits
February 3, 2021 10:20
refatoração da estrutura inicialmente criada para permitir estilos em linha customizados pelo config. atualização do readme com detalhes de como implementar o que foi mudado. 345 / 5000 Resultados de tradução inclusion of optional line break via config. refactoring the structure initially created to allow inline styles customized by the config. update readme with details on how to implement what has been changed. tested code without the new changes maintaining its old and standard functioning. total adaptation to the markdown used in the slack
added 10 commits
February 17, 2022 16:27
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.
I am integrating slack via webhooks into my react application however slack partially uses markdown when I have formatting in the text content. So bold, italic, underline, etc ... need styles different from the standard generated by the library in version 0.6.0. As I needed to solve my problem I thought about sharing my solution in the main project.
Basically the previous version is not affected and nothing is completely changed, not by my local tests.
So whoever needs to integrate a Slack of life like me can change the properties they want generating a final text that is very consistent with what their integration expects.
Another problem was the line break that was not included in the string itself and that in my integration it was necessary to render the text breaks correctly.