Added feature to not overwrite existing handlers if found in core application #170
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 PR introduces a simple change that allows for handlers to be embedded within the application and prevents
vapor-cli
from replacing them upon deployment.Usage
In WinterCMS (a Laravel powered CMS) we utilise our own
autoload.php
which allows us to load our custom helpers before composer loads those provided by Laravel.The core issue (being able to autoload files in a specific order) was recently closed by composer:
composer/composer#6768
Unfortunately when deploying with Vapor, the
httpHandler.php
is injected which calls:This means that our application helpers are replaced by the core Laravel ones.