Autoloader: Improved component path guessing #1928
Merged
Conversation
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
RunDevelopment
changed the title
RunDevelopment
force-pushed
the
autoloader-lang-path-declare
branch
from
528a3ac to
0fe53e0
Compare
mAAdhaTTah
approved these changes
Jul 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This changes the behavior of how the Autoloader handles
data-autoloader-pathattributes and guesses the components path.data-autoloader-pathwill now set thelanguages_pathno matter the content.This fixes Autoloader could work using a CDN #1424.
/\bplugins\/autoloader\/prism-autoloader\.(?:min\.)js$/i, then we will now correctly guess the components path..min.js.The example in #1924 can be simplified after a new version with this change is released.Edit: Done.