Plugins: Consistent Prism check#2788
Merged
RunDevelopment merged 2 commits intoPrismJS:masterfrom Mar 21, 2021
Merged
Conversation
JS File Size Changes (gzipped)A total of 25 files have changed, with a combined diff of -157 B (-0.7%). Details
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Here is a fix for something that bugged me for a long time. All of Prism's plugins now use the same check to determine whether Prism is loaded.
The new check is a simple
typeof Prism === 'undefined'. Theselfvariable is now completely ignored.Checks for DOM access are similar:
typeof document === 'undefined'.I also made the formatting of the check consistent with one empty line before and after it.