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
We have the option to allow users to set their own Query provider instead of Apollo, this works great in production code, but once you're entering testing territory you run into problems.
For Apollo we have a MockProviders function in MockProviders.tsx, this function sets the RedwoodApolloProvider.
To make "Bring your own query provider" more a first class experience we probably want to come up with a solution to be able to either override the RedwoodApolloProvider in MockProviders.tsx, or allowing users to set their own MockProviders.
The text was updated successfully, but these errors were encountered:
I can now import this in my tests instead of the render from redwoodjs/testing. This however doesn't feel like a solid solution, and more of a temporary hack.
We have the option to allow users to set their own Query provider instead of Apollo, this works great in production code, but once you're entering testing territory you run into problems.
For Apollo we have a
MockProviders
function inMockProviders.tsx
, this function sets the RedwoodApolloProvider.To make "Bring your own query provider" more a first class experience we probably want to come up with a solution to be able to either override the RedwoodApolloProvider in MockProviders.tsx, or allowing users to set their own MockProviders.
The text was updated successfully, but these errors were encountered: