Incorrectly generating routes for nested dynamic segments where the first one is optional
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 175
- Forks
- 17
- Avg merge
- 5h 26m
- Merged PRs (30d)
- 5
Description
Given the file
($one,).$two+page.marko
should generate routes
/$two
/$one/$two
but currently generates
/$one
/$one/$two
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the route-generation entry point for Marko files with nested dynamic segments, then reproduce the case using ($one,).$two+page.marko. Confirm the fix produces /$two and /$one/$two, rather than /$one and /$one/$two, and add or run the relevant route-generation test if one exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100