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
Loading a single artist page (such as /artist/lynn-chadwick) results in repeat loads of the artist's API data (so, e.g., 2 requests to /api/v1/artist/lynn-chadwick?).
I'm not sure if these are from the server and client-side, or perhaps from the server and separately via Metaphysics, but ideally the load could happen just once and shared/bootstrapped as necessary for other client contexts.
The text was updated successfully, but these errors were encountered:
Determined that this is indeed from server-side and client-side.
Client-side, we actually don't re-fetch information about the artist, but because our fetches for things like "related artists" and "related shows" comes via the artist schema in metaphysics, metaphysics first fetches the artist in order to grab the ID to pass along through to future requests.
I'm not sure if there's a better way to circumvent this fetch only in the case where you're looking at these subfields, but I suspect not? In any case, this is likely to be cached on metaphysics'-side so hopefully doesn't consistently request this endpoint.
Loading a single artist page (such as
/artist/lynn-chadwick
) results in repeat loads of the artist's API data (so, e.g., 2 requests to/api/v1/artist/lynn-chadwick?
).I'm not sure if these are from the server and client-side, or perhaps from the server and separately via Metaphysics, but ideally the load could happen just once and shared/bootstrapped as necessary for other client contexts.
The text was updated successfully, but these errors were encountered: