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
Embeds seem to be useful as they reduce the amount of API calls needed, but at the same time, they can cause issues with the current Caching implementation, as the elements might already be queried, but the embedded API call has not been done yet. So it causes more queries instead of less queries.
Simply stripping the ?embeds=... from the URL when comparing, doesn't work, because the embedded objects might not be queried yet. If there's more than 1 embedded object that it wants to access, it would cause more queries then. So this isn't really a good solution.
The text was updated successfully, but these errors were encountered:
Embeds seem to be useful as they reduce the amount of API calls needed, but at the same time, they can cause issues with the current Caching implementation, as the elements might already be queried, but the embedded API call has not been done yet. So it causes more queries instead of less queries.
Simply stripping the ?embeds=... from the URL when comparing, doesn't work, because the embedded objects might not be queried yet. If there's more than 1 embedded object that it wants to access, it would cause more queries then. So this isn't really a good solution.
The text was updated successfully, but these errors were encountered: