Skip to content

Names of ng's built in request handlers are too generic, meaning they can clash with generic routes #97

Open

Description

@hugithordarson

Our built in routes (nr,no, na etc) make these path-prefixes unusable in user routes. We should probably be reserving a single "namespace" (first path element) for our built in routes. ng or _ng_ — even making that reserved path customizable.

Activity

  1. changed the title [-]Names of ng's built in request handlers are too generic[/-] [+]Names of ng's built in request handlers are too generic, meaning they can clash with generic routes[/+] on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions