[1.x] Restrict guest Middleware to Fortify's guard #258
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 resolves a conflict with the RedirectIfAuthenticated middleware.
Currently, the guest middleware is added to fortify routes without a specific guard. In some applications, you will be a guest with one guard but authenticated the next.
This PR changes the guest registration on the Fortify guest middleware to use the gust middleware with the guard specified in the Fortify config file.