Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(message-parser): Backtick char in domainChar #861

Merged
merged 2 commits into from
Oct 4, 2022

Conversation

hugocostadev
Copy link
Contributor

TC-104

Proposed changes (including videos or screenshots)

Problem:
Some combinations of inline code with back-stick was resulting in a plain text, the root cause is because the back-stick was being considered a valid character that should be in the Domain Name of an URL

Solution:
Was added a back-stick char into the invalid chars to parse an URL domain name.

Current behavior
image

Expected behavior
image

Issue(s)

Further comments

@guijun13 guijun13 changed the title fix(message-parser): Back-stick char in domainChar fix(message-parser): Backtick char in domainChar Oct 4, 2022
@guijun13 guijun13 merged commit 90fee07 into parser-issues Oct 4, 2022
@guijun13 guijun13 deleted the fix/domainChar branch October 4, 2022 18:35
gabriellsh added a commit that referenced this pull request Oct 5, 2022
* Add first test

* fix: check if is emoticon to preserver colon character

* fix(message-parser): Thumbs emoji becoming phone number (#858)

Co-authored-by: gabriellsh <[email protected]>

* fix(message-parser): Link/URL parser issues (#855)

* feat(fuselage): Adds wordbreak in Box Component (#853)

* Fixing URL/links parsing issues

* restoring files from base branch

* replacing backstick with single quotes

Co-authored-by: Douglas Fabris <[email protected]>

* fixing domainChar accepted chars (#861)

* temporarily removing emphasis support

Co-authored-by: Filipe Marins <[email protected]>
Co-authored-by: Hugo Costa <[email protected]>
Co-authored-by: Douglas Fabris <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants