You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
routeInterceptor can return only string and this is having a lot of disadvantages. You cannot pass any queryParams. If you try to modify the string and append the queryparams to your route, you are going to get: ERROR RuntimeError: NG04002: Cannot match any routes. URL Segment: 'your-route%3FmyQueryParam%3Dtrue'
The query params are getting encoded by Angular router and you are going to get error, because the route is not being recognized.
Describe the solution you'd like
I think that best scenario could be that routeInterceptor would return nothing, but it could be some kind of callback and anybody could wrote its own logic which should be executed when user clicks the link.
I tried to convert queryParams into string and append it to the returned string, but it resulted into that error I described above. So there is no workaround. There is no workaround.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
🧩 Add queryParams support for routeInterceptor
Description
routeInterceptor
can return only string and this is having a lot of disadvantages. You cannot pass any queryParams. If you try to modify the string and append the queryparams to your route, you are going to get:ERROR RuntimeError: NG04002: Cannot match any routes. URL Segment: 'your-route%3FmyQueryParam%3Dtrue'
The query params are getting encoded by Angular router and you are going to get error, because the route is not being recognized.
Describe the solution you'd like
I think that best scenario could be that routeInterceptor would return nothing, but it could be some kind of callback and anybody could wrote its own logic which should be executed when user clicks the link.
Describe alternatives you've considered
I tried to convert queryParams into string and append it to the returned string, but it resulted into that error I described above. So there is no workaround. There is no workaround.
The text was updated successfully, but these errors were encountered: