On staging, if you log in to an account that already has some apiary scores cached, we get this:
This is possibly because the data structure in the front-end has changed, but the data in the back-end was not migrated into the new structure.
We can either:
Write a data migration that reads every existing row and checks if it is in the new format. If not, it adds / removes keys until it is, and saves it.
See if an Apiary with null scores has them fetched automatically. If so, clear out all the old scores and they will be populated as users log back in to the new system.
On staging, if you log in to an account that already has some apiary scores cached, we get this:
This is possibly because the data structure in the front-end has changed, but the data in the back-end was not migrated into the new structure.
We can either:
nullscores has them fetched automatically. If so, clear out all the old scores and they will be populated as users log back in to the new system.