facebook / facebook/docusaurus

active matching to multiple sub paths

Aperta
#8,018 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub
bug
Lingua principale
TypeScript
Stelle
66.2k
Fork
10k
Merge medio
1g 3h
PR unite (30g)
52

Descrizione

### Have you read the Contributing Guidelines on issues?

- [X] I have read the [Contributing Guidelines on issues](https://github.com/facebook/docusaurus/blob/main/CONTRIBUTING.md#reporting-new-issues).

### Prerequisites

- [X] I'm using the latest version of Docusaurus.
- [X] I have tried the `npm run clear` or `yarn clear` command.
- [X] I have tried `rm -rf node_modules yarn.lock package-lock.json` and re-installing packages.
- [X] I have tried creating a repro with https://new.docusaurus.io.
- [X] I have read the console error message carefully (if applicable).

### Description

When using versioned docs with explicit paths (v10 docs are at trpc.io/v10/introduction, v9 at trpc.io/v9/introduction etc), every single sub route of /v10 is active matched from the navbar.

We have some items in the navbar that are doc items (introduction, quickstart and usage with next.js) that are all being marked as active when browsing the documentation.

### Reproducible demo

https://github.com/trpc/trpc/tree/next/www

### Steps to reproduce

1. Go to
2. Click on either any of the nav-items
3. See all of the above being marked active ❌
![CleanShot 2022-08-29 at 00 47 11](https://user-images.githubusercontent.com/51714798/187097696-161ee67b-5f93-4e0b-b218-363732dac79a.png)

### Expected behavior

If clicking quickstart, only that should be marked active etc.

### Actual behavior

all subroutes under `/v10/*` or `/v9/*` is marked active.

### Your environment

- Public source code: https://github.com/trpc/trpc/tree/next/www
- Public site URL: https://trpc.io
- Docusaurus version used: 2.0.1
- Environment name and version (e.g. Chrome 89, Node.js 16.4): Latest Safari, Chrome & Firefox
- Operating system and version (e.g. Ubuntu 20.04.2 LTS): MacOS 12.5.1

### Self-service

- [ ] I'd be willing to fix this bug myself.

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.