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
{{ message }}
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Once the App loads and I navigate to the route via URL it works without issue. URL is /configuration just to note.
However, once I'm on that /configuration module, if I do a hard refresh, it's like the MVC backend kicks in and attempts to resolve the Controller/Action (which obviously doesn't exist)
Am I missing something here? Why would "MVC" be trying to load /configuration instead of letting it fall to Angular?
NOTE: If I change the route to "config" reloading/navigating works as expected. Is something special about "configuration" (seems very odd to me unless I'm overlooking something)
The text was updated successfully, but these errors were encountered:
I'm seeing something strange.
I've followed this to enable Lazy Loading of modules in my App.
7ded0a0
Once the App loads and I navigate to the route via URL it works without issue. URL is /configuration just to note.
However, once I'm on that /configuration module, if I do a hard refresh, it's like the MVC backend kicks in and attempts to resolve the Controller/Action (which obviously doesn't exist)
My MVC routes haven't changed and are base:
Am I missing something here? Why would "MVC" be trying to load /configuration instead of letting it fall to Angular?
NOTE: If I change the route to "config" reloading/navigating works as expected. Is something special about "configuration" (seems very odd to me unless I'm overlooking something)
The text was updated successfully, but these errors were encountered: