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
The route is not found. The cause seems to lie in the fact that the routes is bound as singleton in the boot of the provider and being resolved and pushed to the router in the boot. The extenders are however run after the providers are booted, so hooking into them resolving will be too late.
I changed the following in InstalledSite and that resolved the issue I had locally:
Yep, that fix is correct. (Although we can discuss whether the local extenders should run first, or the ones from enabled extensions. In the latter case - which I prefer - this would have to change slightly.)
Bug Report
Current Behavior
When registering an api route on the root extend.php like this:
The route is not found. The cause seems to lie in the fact that the routes is bound as singleton in the boot of the provider and being resolved and pushed to the router in the boot. The extenders are however run after the providers are booted, so hooking into them resolving will be too late.
I changed the following in
InstalledSite
and that resolved the issue I had locally:to
The text was updated successfully, but these errors were encountered: