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
The instructions have the coder go through the code base and make updates to components based on information coming from the Airtable API. I argue that this is not a best practice. We, as developers, change api services out periodically so should write code that is loosely coupled from our data sources.
The data should be serialized (convert the shape of the data) so that it matches what the application expects. For this specific scenario, a map can convert the response into objects that the code base can already work with.
This is much better than going into the TodoListItem and changing the props for title as that component shouldn't care at all about data inbound from an API.
The text was updated successfully, but these errors were encountered:
The instructions have the coder go through the code base and make updates to components based on information coming from the Airtable API. I argue that this is not a best practice. We, as developers, change api services out periodically so should write code that is loosely coupled from our data sources.
The data should be serialized (convert the shape of the data) so that it matches what the application expects. For this specific scenario, a map can convert the response into objects that the code base can already work with.
This is much better than going into the TodoListItem and changing the props for title as that component shouldn't care at all about data inbound from an API.
The text was updated successfully, but these errors were encountered: