Skip to content

javascript: a chained route link whose path is a constant or template is labelled with the previous link's path #1732

Closed as duplicate

Description

@swapnilpaliwal-sd

Symptom: a chained route link whose path is not a plain string literal is labelled with the PREVIOUS link's path, under its own verb.

Repro (Express):

const PATHS = { item: '/items/:id' };
router.get('/items/all', listItems)
  .get(PATHS.item, getItem)
  .put(`/items/${':id'}`, putItem);

impact getItem → registered as a GET route "/items/all". impact putItem → registered as a PUT route "/items/all".

Expected: the verb with no path, or the constant's value. Only a link chained on router.route(p) takes its receiver's path.
Actual: a confident wrong path, which a test requesting /items/all could join to.

Activity

  1. added
    bugSomething isn't working
    skillAgent-facing query skill (skills/axiomcode)
    on Sep 29, 2026
  2. swapnilpaliwal-sd commented on Sep 29, 2026

    @swapnilpaliwal-sd
    ContributorAuthor

    Consolidated into #1731, which tracks this issue together with related ones about JavaScript route chains and HTTP client request shapes. The description and reproduction here still apply, and the fix for the group covers them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't workingjavascriptJavaScriptskillAgent-facing query skill (skills/axiomcode)

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions