[12.x] feat: add extending env to configure step #55933
Closed
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
This PR extends the work that was implemented in #54756.
Problem
The original PR added functionality for extending the Env with custom adapters. In the current state one needs to add a new line in
bootstrap/app.php
right before the application builder. While this works, it takes a way a bit of the feel of slickness and fluidity of configuring your Laravel application.Proposed Solution
My initial thought was to add a new static method that could be called before
configure
. I quickly came to the conclusion that this is a lot of unnecessary work. I opted instead for adding a new parameter to the method, since extending the environment still falls under the umbrella of "configuration" of the application.This PR introduces a new parameter to
Application::configure
where you can pass an array of callbacks - with keys for names - which will seamlessly add new env adapters to your environment.Example