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
Is your feature request related to a problem? Please describe.
It would be great to be able to change the default authorization/rate limit error message set in the loader.
Main reason - it's a string of no fixed structure and no guarantees that it won't change it the upcoming release. I'd really love to be able to have something like UNAUTHORIZED instead of the Unauthorized request to Subgraph ....
The functions in question are Loader.renderAuthorizationRejectedErrors and Loader.renderRateLimitRejectedErrors.
Describe the solution you'd like
I'd be fine with any way of accessing these errors w/o copying/patching half of the router code. The simplest one would probably be the "override" similar to other error overrides.
Describe alternatives you've considered
No response
Additional context
In general it would be nice to have some access to the resolve.Context created in the GraphQLHandler.ServeHTTP. One option I was exploring was to find a way to set a LoaderHook as there is a call to it right after the auth error is merged. But to set these hooks i'll need to customize the handler, which implies customizing the mux, which implies customizing the startup procedure. Basically too much copy-pasting for a single line of text
The text was updated successfully, but these errors were encountered:
WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.
Component(s)
router
Is your feature request related to a problem? Please describe.
It would be great to be able to change the default authorization/rate limit error message set in the loader.
Main reason - it's a string of no fixed structure and no guarantees that it won't change it the upcoming release. I'd really love to be able to have something like
UNAUTHORIZED
instead of theUnauthorized request to Subgraph ...
.The functions in question are
Loader.renderAuthorizationRejectedErrors
andLoader.renderRateLimitRejectedErrors
.Describe the solution you'd like
I'd be fine with any way of accessing these errors w/o copying/patching half of the router code. The simplest one would probably be the "override" similar to other error overrides.
Describe alternatives you've considered
No response
Additional context
In general it would be nice to have some access to the
resolve.Context
created in theGraphQLHandler.ServeHTTP
. One option I was exploring was to find a way to set a LoaderHook as there is a call to it right after the auth error is merged. But to set these hooks i'll need to customize the handler, which implies customizing the mux, which implies customizing the startup procedure. Basically too much copy-pasting for a single line of textThe text was updated successfully, but these errors were encountered: