-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix: Opening remarks with built-in quick Q&A and tag conflicts result in HTML rendering failure #2183
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
Merged
Merged
fix: Opening remarks with built-in quick Q&A and tag conflicts result in HTML rendering failure #2183
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
The provided code appears to be a complex function that attempts to process a
prologue
property and replace certain patterned content with another type of question. Some issues include:Performance Overhead: The approach used is inefficient because it uses regular expressions multiple times across the entire text without optimizing for specific patterns.
Simpler Regular Expression: Instead of using an array of regexes, you could combine them into one large regex to simplify processing time and reduce complexity.
Missing Error Handling: No checks are made to ensure that
props.available
orprops.application?.prologue
exists before attempting to access their properties.Return Type: It would be beneficial to specify TypeScript types for variables like
result
,_temp
, andquick_question_list
.Here's an optimized version:
Explanation of Changes:
<tag>
patterns into a single regex (/<(html|echarts|rander).*?<\/\1>/gi
)..item(0)
to get the first<quick_question>
tag instead of accessing an indexer on an HTMLCollection, which is more reliable.document.createElement()
instead of assumingElement
is defined; this should work depending on your context but might need adjustment based on exact usage requirements.This refactored version maintains readability and improves performance by avoiding unnecessary repeated operations. However, the actual behavior may vary if other parts of your application rely on different DOM elements or structures.