Skip to content

Docs: orphaned partials not referenced by the v3 docs manifest #5184

@norman-abramovitz

Description

@norman-abramovitz

Issue

Two documentation partials exist in the tree but are not referenced by the v3 docs manifest (docs/v3/source/index.html.md), so they appear to be dead files. Flagging for confirmation/cleanup.

Context

Found while extracting a structured model from the v3 docs (which walks the manifest's includes: list). These two partials are present on disk but never referenced:

  • docs/v3/source/includes/api_resources/_route_mappings.erb — the route_mappings resource is no longer in the manifest.
  • docs/v3/source/includes/upgrade_guide/conceptual_changes/_ports.md — not referenced by the manifest.

Both are present at current main HEAD.

A minor related naming nit (no functional impact): docs/v3/source/includes/resources/spaces/get_assigned_isolation_segment.md.erb is the only spaces partial lacking a leading underscore. The manifest references it like a normal partial and it still renders, so this is cosmetic/consistency only.

Steps to Reproduce

  1. Open docs/v3/source/index.html.md and note the includes: manifest list.
  2. Grep the manifest for route_mappings and conceptual_changes/ports — neither is referenced.
  3. Confirm the two files still exist under docs/v3/source/includes/.

Expected Result

The docs tree contains only partials referenced by the manifest.

Current Result

Two orphaned partials remain in the tree.

Possible Fix

Remove the two orphaned partials. Optionally rename the spaces partial to _get_assigned_isolation_segment.md.erb for consistency. Happy to open a PR if you'd like.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions