Add support for class-based replacements instead of closures #2119
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.
Hi,
In this pull request (related to #2040), I added support for using class-based replacements instead of Closures.
Previously, when using Closures in replacement configuration, running the
php artisan config:cache
command caused the following error:To solve this, I introduced a new
ReplacementKeyCommand
class.Replacements can now be implemented as dedicated classes, ensuring compatibility with config caching.
Example
Replacement classes:
Config file usage:
This resolves the serialization issue and makes replacements more extendable and testable.
Fixes #2117.