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
Ideally we want to use some package for data fetching. However, after doing some research, this was my findings:
After looking into this a bit more, implementing react query is more complicated than anticipated. In some apps we would end up with two query clients. It is possible to have more than one query client in an application, but the application's own query client would typically be in App.tsx, while core's query client would be in our navigation system. This means that mad-core's query client would be closer to the screens in the hierarchy, which means mad-core's query client would be used by default.
So there have multiple ways to implement this:
Export a query client from mad-core and tell the developers to put it above their own query client in the hierarchy. Internally in mad-core we would use that query client, but it won't be used by default in other parts of the app (unless the developers want to use it).
Put the query client inside the the core system, and tell the app developers to explicitly use their own context if they have their own query client.
If anyone has any suggestions on how we should proceed with data fetching in mad-core, please leave a comment here
Alternatives
No response
Other info
No response
The text was updated successfully, but these errors were encountered:
Package / App
Other
Description
Ideally we want to use some package for data fetching. However, after doing some research, this was my findings:
If anyone has any suggestions on how we should proceed with data fetching in
mad-core
, please leave a comment hereAlternatives
No response
Other info
No response
The text was updated successfully, but these errors were encountered: