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
It would be helpful to include more metadata in the GRAPHQL section in the debug panel – currently it's impossible to know the "source" of a given query (e.g. a client-side hook called from configurator-state.tsx file to populate urql cache).
The idea would be to be able to pass e.g. a "queryReason" and "querySource" properties to urql hooks, that would be passed down the road to GQL server, which would include them in extensions shown in the debug panel.
With this change, we would be able to more easily investigate why a particular query was made, and how we could potentially improve the whole data fetching flow.
It would be helpful to include more metadata in the GRAPHQL section in the debug panel – currently it's impossible to know the "source" of a given query (e.g. a client-side hook called from
configurator-state.tsx
file to populate urql cache).The idea would be to be able to pass e.g. a "queryReason" and "querySource" properties to urql hooks, that would be passed down the road to GQL server, which would include them in
extensions
shown in the debug panel.With this change, we would be able to more easily investigate why a particular query was made, and how we could potentially improve the whole data fetching flow.
cc @Rdataflow
The text was updated successfully, but these errors were encountered: