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
Hey, I switched to using this middleware (and whooops) also for APIs. Endpoints accessed by javascript that encounter an exception get a 500 error message - see discussion in filp/whoops#666 ... I'd basically need to extend the PrettyPageHandler ... I guess that
adding support for a variable PrettyPageHandler
adding the ability to pass custom headers via a config option
or similar
might do the trick. Or do you see another way around?
Thanks
The text was updated successfully, but these errors were encountered:
Thank you for your question. Please let me make some assumptions first.
In this case, if you are using the Slim framework on the backend (API) only. The frontend also base on the React, Vue or another frontend library/framework and managed via Webpack/Vite. The frontend application can call the api through the proxy in development environment.
In the production environment, the slim whoops plugin should be disabled by default.
Hey, I switched to using this middleware (and whooops) also for APIs. Endpoints accessed by javascript that encounter an exception get a 500 error message - see discussion in filp/whoops#666 ... I'd basically need to extend the PrettyPageHandler ... I guess that
might do the trick. Or do you see another way around?
Thanks
The text was updated successfully, but these errors were encountered: