[X] Member Count placeholder shown on gym search page on FE
[x] Need BE endpoint to send data -- see BE issue and/or linked PR for issue #67 for exactly how the data will be returned
[x] Need FE to finish update
Might be nice to show on the gym search page how many active members are at the gym.
This should be handled on the backend and then the gym poro could have an attribute added for gym_member_count.
TV 10.8: Going with attribute on this. The serializer is hand-rolled anyways.. no point (IMO) in keying this out as meta when we can just add another attribute.
Note:
We could update the Gym Search endpoint to send meta information along with each gym in the GymSerializer.
That meta information would be a hash key that populates the gym member count.
Method as something like:
Might be nice to show on the gym search page how many active members are at the gym.
This should be handled on the backend and then the
gymporo could have an attribute added forgym_member_count.TV 10.8: Going with
attributeon this. The serializer is hand-rolled anyways.. no point (IMO) in keying this out asmetawhen we can just add anotherattribute.Note: We could update the Gym Search endpoint to send
metainformation along with each gym in theGymSerializer.That
metainformation would be a hash key that populates the gym member count. Method as something like:See @tvaroglu or @Scott-Borecki for help with using
metain the the serializer. Or check out the jsonapi-serializer docs: https://github.com/jsonapi-serializer/jsonapi-serializer#meta-per-resource