Add support for Dotenv v3, v4, and v5 #25
Merged
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.
Checklist:
Description
Adds support for Dotenv v5 while also keeping support for v4 and restoring support for v3.
This allows older projects that might be stuck on an older version of Dotenv to continue to benefit from updates to this Composer plugin.
How has this been tested?
I'm testing this on a client project that uses Advanced Custom Fields Pro, Gravity Forms, and Polylang Pro.
Types of changes
Added
Installer::loadDotenv()
to resolve and instantiate the currently available version of theDotenv
class.AbstractPlugin
as basis for all supported WP plugins. The class provides aget()
method which serves as a wrapper ofgetenv()
that will throw an exception if the requested environment variable is missing.MissingEnvException
in case an environment variable is missing.Changed
AbstractPlugin
and use itsget()
method instead of directly usinggetenv()
function.