Repository navigation
Commit ee4669a
committed
docs: Do not register category fragments
This is causing a name collision on category names when building header
links in the documentation. The "category" names are being registered in
get_fragment even though the header patterns for Events and Requests are:
* `## {} Events`
* `## {} Requests`
As a result, when processing Requests, the shared categories between
Events and Requests, such as "General" and "Config", end up with
"deduplicated" names for the header links such as:
* general-1-requests
* config-1-requests
This results in broken links in the Requests Table of Contents.
Since the categories themselves are not used to build links anywhere, we
can set the register param in those get_fragment(category) calls to
False and only register the requestType and eventType fragments.1 parent 69d41b8 commit ee4669a
1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
162 | 162 | | |
163 | 163 | | |
164 | 164 | | |
165 | | - | |
| 165 | + | |
166 | 166 | | |
167 | 167 | | |
168 | 168 | | |
| |||
227 | 227 | | |
228 | 228 | | |
229 | 229 | | |
230 | | - | |
| 230 | + | |
231 | 231 | | |
232 | 232 | | |
233 | 233 | | |
| |||
0 commit comments