Closed fireflysemantics closed 1 year ago
Similar to https://github.com/analogjs/analog/issues/273
You can define route paths as src/app/pages/[category].[topic].page.ts
for the equivalent route.
Hi Brandon,
I also thought this would work:
You can define route paths as src/app/pages/[category].[topic].page.ts for the equivalent route.
So I tried it with this application:
https://github.com/fireflysemantics/analog-project/tree/main/src/app/pages
And if I enter the URL:
http://localhost:5173/blog/1234
It renders the right page. However if I try to match this route:
/[productId].[partid].page.ts
With a URL like:
http://localhost:5173/1234/1234
It reroutes to the error page. Thoughts?
Which scope/s are relevant/related to the feature request?
create-analog
Information
Currently all dynamic routes in AnalogJS have to be in a parent folder or prefixed with a parent path.
I have an app that defines a route like this:
And it renders URLs like this:
And these routes are currently being statically rendered by Scully.
If I switch to AnalogJS, I'd have to create a component for each category even though they can all be handled by the same component:
Describe any alternatives/workarounds you're currently using
Currently using Scully.
I would be willing to submit a PR to fix this issue