I'm experiencing somewhat of a bug with Ember/Ember-data. Here's my scenario:
-
Client lands on
/
route and Ember loads data from/api/v1/videos?limit=8
. The response comes from a rails-api backend using active_model_serializers which ensures the response is JSON API compliant. Now the store has 8 arbitrary videos loaded into it. -
Each video component in the DOM has a link to a user page (the user
hasMany
videos. Client clicks on alink-to
which navigates to/stores/1
which represents a user with ID 1 -
The model hook for that route just loads a single user record. The user record has the following payload:
{ "data": { "id": "1", "relationships": { "videos": { "data": [], "links": { "related": "/api/v1/videos?user_id=1" } }, }, "type": "users" } }
The problem is that ember does not automatically send the request for /api/v1/videos?user_id=1
(presumably because a similar request /api/v1/videos?limit=8
already happened).
If I directly load the /stores/1
page then ember is smart and auto-loads data from the /api/v1/videos?user_id=1
endpoint.
I suspect that Ember is being fooled by the fact that a similar request to the videos endpoint already happened with different query parameters. The end result is that my app does not show any data on the user page.
One way to fix this is to populate "data": [],
with video IDs which will cause ember to send n requests for n items. This works but is not acceptable for a large scale app where a user page might have 100 videos.
How can I fix this?
Aucun commentaire:
Enregistrer un commentaire