Makes Vapor UI middleware customizable #23
Merged
Conversation
This file contains 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
Co-Authored-By: ugurgungezerler <6935893+ugurgungezerler@users.noreply.github.com>
nunomaduro
changed the title
Closed
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.
This pull request was co-authored by @ugurgungezerler and it adds the possibility of having the Vapor UI middleware stack be overridden at userland - using
config/vapor-ui.php. Very similar to what we do have in Telescope.Note that by default, the
vapor-ui:installArtisan command won't publish thevapor-ui.phpconfig file. But the user can easily do it by runningart vendor:publish --tag=vapor-ui-config. We are going to update docs in this regard.Closes #13.
This pull request should be squashed.