Fix route().current()
with wheres including regex start/end anchors
#535
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 updates Ziggy to strip any leading/trailing
^
and$
regex anchor tokens from route parameter 'where' constraints before attempting to compile a route pattern. Previously, a route with something like->where('parameter', '^(?!nova-api|nova-vendor)$')
would eventually end up with Ziggy's javascript attempting to match something likeziggy.dev/(?<parameter>^(?!nova-api|nova-vendor)$)/path
, which would never match anything. Now, it producesziggy.dev/(?<parameter>(?!nova-api|nova-vendor))/path
.Laravel (via Symfony) already strips these out before it does any route matching, so they're not actually doing anything there (Symfony's
Route
, which Laravel'sRoute
uses internally when matching). This PR brings Ziggy in line with this behaviour.Fixes #534.