`useMatchRoute({ to: ... })` is used with default (exact) matching to compute `isActive`. This changes behavior from the previous `NavLink` (which was active for nested routes) and will likely cause tabs like “Sets” to not appear active on nested routes (e.g. set details) and “Schedule” to not appear active on `/schedule/timeline` or `/schedule/list`. Consider using fuzzy/partial matching (e.g. `fuzzy: true`) or Link `activeOptions` so parent tabs stay active for descendant routes.

[chiptus]

useMatchRoute({ to: ... }) is used with default (exact) matching to compute isActive. This changes behavior from the previous NavLink (which was active for nested routes) and will likely cause tabs like “Sets” to not appear active on nested routes (e.g. set details) and “Schedule” to not appear active on /schedule/timeline or /schedule/list. Consider using fuzzy/partial matching (e.g. fuzzy: true) or Link activeOptions so parent tabs stay active for descendant routes.

Originally posted by @Copilot in #25 (comment)