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
{{ message }}
This repository has been archived by the owner on Nov 2, 2019. It is now read-only.
Instead of always pulling directly from the API, establish (or find) a service that that will cache our resources loaded from the API on the front-end, so that we can comfortably make tiny requests with impunity. A great use case for this is to simply look up the information needed to display a linked field by its rules under #71, instead of just showing its ID. It seems a bit wasteful to do that for every linked field, but if that data is then stored to be useful later, it's not so bad.
The text was updated successfully, but these errors were encountered:
We can do this very easily as it turns out! Although this is URL-based; it's not intelligent to the resource we're fetching, so a fetch of a single resource won't look up a previous fetch of the whole collection. It's still definitely an improvement, though, and we could get that behavior by maybe making a very simple wrapper on top of this.
Instead of always pulling directly from the API, establish (or find) a service that that will cache our resources loaded from the API on the front-end, so that we can comfortably make tiny requests with impunity. A great use case for this is to simply look up the information needed to display a linked field by its rules under #71, instead of just showing its ID. It seems a bit wasteful to do that for every linked field, but if that data is then stored to be useful later, it's not so bad.
The text was updated successfully, but these errors were encountered: