-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
#2498 - Fix the link bug in the chat #2499
Conversation
group-income Run #3673
Run Properties:
|
Project |
group-income
|
Branch Review |
sebin/task/#2498-chat-link-issue
|
Run status |
Passed #3673
|
Run duration | 10m 47s |
Commit |
f4ac52156d ℹ️: Merge ab5ebabc0d0a65d82f13520cc3e08ded71fbe96b into 191962e2ef071555140018062026...
|
Committer | Sebin Song |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
10
|
Skipped |
0
|
Passing |
112
|
View all changes introduced in this branch ↗︎ |
@@ -87,9 +88,14 @@ function createRecursiveDomObjects (element: any): DomObject { | |||
nodeObj.children.push(createRecursiveDomObjects(child)) | |||
} | |||
|
|||
nodeObj.children = nodeObj.children.filter( | |||
child => child.tagName || (child.text || '').trim().length |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taoeffect Had more thorough investigation for the original issue and found out trim()
here was the cause of the issue. As far as I remember, this was added to remove unnecessary \n
created from `DOMParser: parseFromString() API. So updated the logic here.
@taoeffect Updated the PR with the better fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nicely done @SebinSong !!
closes #2498