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
When /messages/abc is matched, the Match result only indicate that the route :message-detail was matched. Sometimes it's useful to also have all the "parent" routes above it available as a vector.
The proposed workaround of having a custom key (like :section which could be either a set or a vector) is good enough for me, and potentially solves my use case even better, so perhaps this is a moot issue anyway.
The text was updated successfully, but these errors were encountered:
When having a route structure like so:
When
/messages/abc
is matched, theMatch
result only indicate that the route:message-detail
was matched. Sometimes it's useful to also have all the "parent" routes above it available as a vector.The proposed workaround of having a custom key (like
:section
which could be either a set or a vector) is good enough for me, and potentially solves my use case even better, so perhaps this is a moot issue anyway.The text was updated successfully, but these errors were encountered: