Refactor away from object.attribute pattern when handling API responses
aaronpolhamus opened this issue · comments
There are a few places in the frontend--namely the place order form--where we ping the API, get a bunch of data, and then reference that detailed object with an Object.attribute pattern. Apparently this is bad, and there are multiple places in the code where this has made the application more brittle.
Do this properly (see BalancesChart and FieldChart) when there's a chance.