Repository navigation
feat: serve tag pages at their hierarchy path - #296
Merged
Merged
Conversation
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://feat-api-route-conventions.nimbus-docs.com (commit d2531fd)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
MohamedH1998
changed the title
MohamedH1998
force-pushed
the
feat/api-route-conventions
branch
from
October 24, 2026 21:25
b3d9a9d to
3f55334
Compare
An API with nested tags had every section page at tags/<segment>, so a site that publishes landing pages per product and resource could only redirect to them. routes.sections: "hierarchical" routes a tag page at its ancestors' segments then its own, dropping a parent prefix a child tag repeats, and routes.tagSegments renames one tag's segment. Opt-in under resource-action-v2; coordinates and operation URLs do not change.
MohamedH1998
force-pushed
the
feat/api-route-conventions
branch
from
October 24, 2026 21:49
3f55334 to
9369387
Compare
MohamedH1998
added this pull request to stack #297
October 24, 2026 21:51
MohamedH1998
force-pushed
the
feat/api-route-conventions
branch
from
October 24, 2026 22:02
9369387 to
5ef4cd9
Compare
MohamedH1998
changed the title
MohamedH1998
force-pushed
the
feat/api-route-conventions
branch
from
October 24, 2026 22:09
5ef4cd9 to
796f348
Compare
github-actions
Bot
removed
the
pr preview
commit: |
A collision between a tag page and another page only suggested renaming or a routes.operations override, which cannot address a tag. The error now also names routes.tagSegments, and the routes guide lists every reserved first segment.
github-actions
Bot
removed
the
pr preview
MohamedH1998
marked this pull request as ready for review
October 25, 2026 09:57
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Opt-in
routes.sections: "hierarchical"serves each tag page at the path its tag hierarchy spells,/api/zero-trust/devices/ip-profilesinstead of/api/tags/zero-trust-devices-ip-profiles. The default stays byte-identical.Decision: adopt, and land before the Cloudflare API site goes live, since it moves 1,197 tag URLs. Fourth PR of the stack.
Changes
sections: "hierarchical"joins each tag's segment along its parent chain, strips the parent's name from a child that embeds it, and skips page-less grouping tags.tagSegmentsrenames one tag's segment, for a tag whose path would land on a reserved segment.tagSegmentskey, ortagSegmentsunder the frozenresource-action-v1convention each fail with the remedy named, includingroutes.tagSegmentswhen a tag is one side.patch: the default is byte-identical, so the stack releases as one patch.Validation
nimbus-docssuite.