Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent pitfalls in route configuration #18

Open
CathalMullan opened this issue Aug 2, 2024 · 0 comments
Open

Prevent pitfalls in route configuration #18

CathalMullan opened this issue Aug 2, 2024 · 0 comments

Comments

@CathalMullan
Copy link
Contributor

CathalMullan commented Aug 2, 2024

Think of edge-cases which we can't/shouldn't support.
e.g.

  • touching dynamic parameters /{1}{2}
  • two routes ending in a dynamic: /{1}, /{2}
  • wildcard next to wildcard: /{*1}/{*2}
  • wildcards inline: /abc-{*1}

Worth delaying until we are feature complete for path routing.
Constraints will complicate things.

Will be hard to get right on first try.

See the path_tree test: repeated_single_named_param

@CathalMullan CathalMullan changed the title Try and remove ambiguity from routing Prevent pitfalls in route configuration Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant