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
In development of a MCVE, I discovered that when one attempts to use the built in Object Dispatching mechanism on an url such as '/movies/', Webcore delivers a 404 response and navigating to '/movies' correctly renders as a call.
After some discussion, it appears that the splitting of the provided path occurs twice and the second instance does not handle a case where the split will return a single-element empty string on an empty string split and subsequently passed to RemainderArgsExtension.
The text was updated successfully, but these errors were encountered:
In development of a MCVE, I discovered that when one attempts to use the built in Object Dispatching mechanism on an url such as '/movies/', Webcore delivers a 404 response and navigating to '/movies' correctly renders as a call.
After some discussion, it appears that the splitting of the provided path occurs twice and the second instance does not handle a case where the split will return a single-element empty string on an empty string split and subsequently passed to RemainderArgsExtension.
The text was updated successfully, but these errors were encountered: