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
Previously, the rendering of `DataProxyProvider` children were
conditioned by the initialization of the dataproxy.
It was because we wanted to avoid timing issues, were the App started to
use the DataProxy before it was actually ready. See
https://github.com/cozy/cozy-libs/commit/bdb1670
We later made it less strict, because if anything make the dataproxy not
initialized, nothing is displayed on the app side with no logs, making
it hard to debug for the developer. See
#2801
However, we still met situations with no rendering, because the
dataproxy was not available at all:
- Public sharing: cozy/cozy-drive#3439
- Unsupported shared workers:
cozy/cozy-web-data-proxy#36
So now, we always render children, and expect the `DataProxyLink` to
handle queries made on non-ready DataProxy by queuing them:
cozy/cozy-client#1622
0 commit comments