You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2018. It is now read-only.
I understand why a parent fragment would act as a greedy match because we want to render all the content within nested fragments. The problem I have is that it is matching strings as if they were written like /parent-route-string* and not /parent-route-string(/*). So a fragment with forRoute='/parent-route-string' matches /parent-route-string-and-some-more-text-here which seems like a bug.
The text was updated successfully, but these errors were encountered:
I understand why a parent fragment would act as a greedy match because we want to render all the content within nested fragments. The problem I have is that it is matching strings as if they were written like
/parent-route-string*
and not/parent-route-string(/*)
. So a fragment withforRoute='/parent-route-string'
matches/parent-route-string-and-some-more-text-here
which seems like a bug.The text was updated successfully, but these errors were encountered: