-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
fix(routes): fix nested dynamic routes path #305
fix(routes): fix nested dynamic routes path #305
Conversation
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
added the g regexp flag since by default only the first occurrence is replaced.
Thanks! @allcontributors add @yassernasc for code |
I've put up a pull request to add @yassernasc! 🎉 |
@yassernasc this fix has been released in |
Added the g regexp flag since by default only the first occurrence is replaced.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Which package are you modifying?
What is the current behavior?
With a route file with name
route.[route-id].subroute.[subroute-id].ts
, Analog produces the routeroute/:route-id].subroute.[subroute-id]
.Issue Number: N/A
What is the new behavior?
Now Analog produces the route
route/:route-id/subroute/:subroute-id
correctly.Does this PR introduce a breaking change?
Other information