fix: prevent error when users install the plugin from Composer #179
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
…mposer will put the autoload file elsewhere. - Add a check for the Document class in `can_load_plugin` to ensure the autoloaded classes exist before using them
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When installing the plugin from Composer, the autoload.php will exist in the project installing the plugin, not in the plugin itself.
This wraps the the autoload
requirein afile_exists()check before requiring the local plugin autoload.Additionally, this adds a check for the
Documentclass in thecan_load_pluginfunction to ensure the autoloaded classes exist before using them.Closes #176