fix(prism): apply syntax highlighting to dynamically created code elements #9
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.
Summary
Fixes #8 - Prism.js styles not applying on form submit.
When users change secondary languages and click Compare, the syntax highlighting styles were not applied until page reload.
Changes
custom-${lang}tolanguage-${lang}to match Prism.js expected patternPrism.highlightAllUnder(section)increateLiSection()to apply highlighting to dynamically created elementsTechnical Details
The fix addresses two issues:
language-xxxx, notcustom-xxxxBy using
Prism.highlightAllUnder(section)withincreateLiSection(), highlighting is applied efficiently to newly created elements only, improving performance.Closes #8