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
When navigating to nonexistent route in a scope, I'd expect to get the nearest default route that is defined.
Current Behavior
Currently, when a scope does not have a default service set up, it will serve the default service set up in the app (or empty 404 if not set up).
Possible Solution
Look for closest definition of default service while "climbing" down the scopes.
Steps to Reproduce
If we setup routes like so:
/ - our root
~default service
/app scope:
/ - root of app scope
~default service for app scope
/deep scope:
/ - root of deep scope
~no default service
If we navigate to /app/something, we'll end up on the app scope's default service.
However, if we go to /app/deep/something, we end up on the topmost default service. (I'd expect to end up on the app scope's default service).
I encountered this behavior when working on a web shop project, where route something like: /products/something/details-scope/nonexistent, I'd end up with the default response from the server, which had nothing to do with the products...
If this is entirely intended, please just correct me. Otherwise, maybe it would be possible to configure the behavior of the default service resolution in scopes?
The text was updated successfully, but these errors were encountered:
Expected Behavior
When navigating to nonexistent route in a scope, I'd expect to get the nearest default route that is defined.
Current Behavior
Currently, when a scope does not have a default service set up, it will serve the default service set up in the app (or empty 404 if not set up).
Possible Solution
Look for closest definition of default service while "climbing" down the scopes.
Steps to Reproduce
If we setup routes like so:
If we navigate to
/app/something
, we'll end up on theapp scope's
default service.However, if we go to
/app/deep/something
, we end up on the topmost default service. (I'd expect to end up on the app scope's default service).Code
Context
I encountered this behavior when working on a web shop project, where route something like:
/products/something/details-scope/nonexistent
, I'd end up with the default response from the server, which had nothing to do with the products...If this is entirely intended, please just correct me. Otherwise, maybe it would be possible to configure the behavior of the default service resolution in scopes?
The text was updated successfully, but these errors were encountered: