Home Search Pricing Get inErrata About

Sign in Sign up

Graph/route-path-alias-mismatch

AntiPattern

Conflicting Parameter Aliases

route-path-alias-mismatch

A recurring naming-alias mismatch where runtime parameter binding expects the route’s original placeholder while developers override names (via aliases), leading to missing parameters or validation failures and pushing fixes toward schema/OpenAPI customization or convention-only naming.

Node Details

Public graph metadata

Updated4/30/2026

Connections

30 linked nodes

MATCHESSolution

Rename the component/export to use PascalCase (e.g., `const Partners = () => {} export default Partners;`) so Fast Refresh can apply without doing full reloads.

MATCHESSolution

this doesn't work for tanstack router. For example, I have a dynamic route `/items/$itemId.tsx`. Tension: it gives me an error that `$itemId.tsx` should be in kebab-case. Outcome: override Biome config to disable this rule in `routes`.

MATCHESSolution

Configure Next.js middleware to match /api/:path* so requests can be tracked and routed consistently

MATCHESSolution

the convention for tanstack router is indeed to prefix components with `-` — I don't want the page Component file (Home.tsx) to be factored in for routing. Tension: This way this file is ignored. Outcome: It looks like the convention for tanstack router is indeed to prefix components with `-`:.

MATCHESSolution

use hash-based routing — react + tanstack router + github pages. Tension: The default "browser" routing will exhibit the behaviour you describe.

MATCHESSolution

Configure matching alias paths in root and app tsconfig files

MATCHESSolution

"overrides":{ "rxfire>tslib": "2.1.0" } — package.json file. Outcome: This fixed the issue.

MATCHESSolution

After many hours bashing my head against this, I ended up just using the package name itself as an alias.

MATCHESSolution

Set redirect_slashes=False and add both "" and "/" route decorators so both /api/users and /api/users/ work reliably

MATCHESSolution

After changing the route name to all lowercase (`sign-in`) in the main branch and redeploying — the route name in the code was `sign-in`, but on GitHub, I had accidentally pushed it as `Sign-in`. Tension: Since Next.js is case-sensitive with routes, this mismatch caused the deployed version on Vercel to fail. Outcome: everything started working fine.

MATCHESSolution

Just renamed from `api` to `api_src` and it fixed it — one at the root level and the other inside `pages` directory. Tension: two directories called `api`. Outcome: it fixed it.

MATCHESSolution

override Build command to `npx prisma generate && next build` — under Build & Development Settings. Tension: API route failed. Outcome: Redeploy the app.

MATCHESSolution

Rename the server actions directory to a non-reserved name (i.e., not `/api`); after renaming, Links returned to proper client-side navigation and full reloads stopped.

MATCHESSolution

Fix the imports to consistently reference the same module path (e.g., remove the `src.` prefix or otherwise ensure identical import paths for the `Document` model used during initialization and in route handlers).

MATCHESSolution

Do not use `alias` with `Path` parameters in this setup; rely on the function parameter name for the path variable. If you need different naming only in Swagger/UI, customize/override the generated OpenAPI schema instead of using `alias`.

MATCHESSolution

Define a TypeAlias with Annotated[..., Field(union_mode='left_to_right')] and use it instead of a bare Union

MATCHESSolution

Use model_json_schema(ref_template="#/components/schemas/{model}") instead of schema() when building openapi_extra

MATCHESSolution

rename your entities: ACK is your model name and the name of it's field. — ack_message = ACK( message=success_text, id=domain_id, temp_password=instance.domain_hashed_password, ). Tension: value for ACK field was not specified. Outcome: So this line will definitely cause an error.

MATCHESSolution

Define `id` as a non-input private attribute (hidden from validation/schema) and generate it server-side using `PrivateAttr` (with `default_factory` for dynamic defaults). Keep `name` as the only public validated input field; the endpoint can still accept the original model type for consistent validation of `name`.

MATCHESSolution

this issue also occurs if you use the rulesets feature in github to ensure specific branch name — rulesets feature in github. Tension: you will need to add the prefix in this feature too. Outcome: you will need to add the prefix in this feature too.

MATCHESSolution

Predefine the full mapping in a single input (e.g., provide combined options like `A:1`, `A:2`, `B:3`, `B:4`) or use separate inputs for each branch (e.g., `numberA`/`numberB` with their own fixed options). If you need dynamic branching with approvals, model it via chained jobs and GitHub Environments deployment protection rules.

MATCHESSolution

"ParameterName": "Delimiter", "ParameterValue": "\n". Tension: what is the terraform equivalent parameter for enabling "New line delimiter". Outcome: parameter_value = "\\n".

MATCHESSolution

`injected` is not the solution — there is a projection type of `injected`. Tension: it requires the query to provide the values to replace the placeholders in the location template. Outcome: it won't automatically get them from S3 prefixes.

MATCHESSolution

advanced: { database: { generateId: false, }, } — This advance properties fixed my issue. Tension: I attempted to override the UUID generation in the DrizzleAdapter configuration. Outcome: This advance properties fixed my issue.

MATCHESSolution

You don't need to use the same name for both. Tension: it also ships with a new `combineSlices` api. Outcome: in most cases you probably shouldn't deviate unless you have a reason.

MATCHESSolution

The placeholder must not have the parenthesis around, so it must be `(VALUES :ids)`. Outcome: passing `Collection ids` instead of `Collection ids`.

MATCHESSolution

If this is not feasible, the namespace variant should be used. — Distributed applications generating UUIDs at a variety of hosts. Tension: must be willing to rely on the random number source at all hosts. Outcome: the namespace variant should be used.

MATCHESSolution

if any parameter values also contain single quotes — requests that use single quotes. Tension: those must be double escaped. Outcome: replace single quotes by double single quotes until the bug is fixed.

MATCHESSolution

You should be using relative paths. — render a set of "common" routes both under the root `"/"` path and also under the `"/admin"` path. Tension: This will allow you to move a route around anywhere and it will always match relative to its parent route.

MATCHESSolution

Avoid using `undefined` for absent values in args; use a serializable sentinel like `null` (or empty string/number) and adjust the prop/arg union types accordingly so the story file and URL can be merged without breaking the type invariant.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata