-
-
Notifications
You must be signed in to change notification settings - Fork 211
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
Catch-all Routes can't be passed as input #1016
Comments
You won't be able to use the router input bindings here because a catch-all route isn't captured as a route parameter. You can use the https://stackblitz.com/edit/github-wjglg2-5fczvg?file=src%2Fapp%2Fpages%2F[...product].page.ts |
@brandonroberts , thank you for the explanation. I think the documentation needs to be updated to make sure others are not making the same mistakes. and I can create one example of integration with Localess Headless CMS. |
I found another issue when I had only one page with catch-all pages and Server-Side Data Fetching for that page. I'm receiving a next error. I have updated the example also
|
@alexcibotari was this on StackBlitz or locally? The full server environment is not enabled on StackBlitz yet |
Please provide the environment you discovered this bug in.
https://stackblitz.com/edit/github-wjglg2?file=src%2Fapp%2Fpages%2F%5B...product%5D.page.ts
Which area/package is the issue in?
router
Description
I consume a Headless CMS Localess: https://github.com/Lessify/localess
For that, I created one route that would capture all routes and fetch data via API using the feature: Using Route Component Input Bindings
For the moment the feature works only for dynamic routes, which limits me only to a one-page level, where I actually would like to be able to capture all possible routes.
Dynamic Rout will work with the next
But it will not be able to handle next
Please provide the exception or error you saw
No response
Other information
Same time ActivatedRouteSnapshot.params is empty
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: