[1.x] Consistently use verified
middleware on /dashboard
route.
#190
+1
−1
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.
The Vue and React stacks have the
verified
middleware on the/dashboard
route by default:breeze/stubs/inertia-common/routes/web.php
Lines 27 to 29 in c478aba
This PR updates the Blade stack to be the same. Note that it only takes effect if the
MustVerifyEmail
interface is implemented on theUser
model.It's obviously a personal preference whether or not the dashboard should require verification, so an alternative would be to remove it from the other stacks. Personally, I like that it's there by default as it's safer and demonstrates a feature that Breeze provides UI components for.