Vulcain support for reference fields/inputs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react, typescript
Research direction
Start with ReferenceField and ReferenceInput, then compare their calls with useGetList, useGetOne, useGetMany, and the dataProvider path. Done means establishing whether Vulcain’s Preload header can be supplied for these relationship loads, or documenting the supported usage.
Written by the indexing model from the issue text.
Description
Description
Hey! I am currently using APIP with this admin package to build a UI on top of my API. Most of my resources have multiple many-to-one or many-to-many relationships, which end up on each screen (show, create, edit). I'm using the default <ReferenceField /> and <ReferenceInput /> to load these relationships, but these end up making quite a few additional API calls which slows down page render.
If I understood correctly, Vulcain could help combat this issue by hitting the API once, and passing an additional header specifying which additional resources to pass in the response. However, this doesn't seem possible with my set-up, as I'm not calling the dataProvider directly (it is done by the reference components) and cannot specify the header for Vulcain.
Or maybe I am missing something. Should I not be using the <ReferenceField />/<ReferenceInput /> in this case? Would it be possible to pass the Preload header if I use the dataProvider methods directly? (eg. useGetList, useGetOne, useGetMany etc)
Thanks.
- Dominant language
- TypeScript
- Stars
- 516
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from api-platform/admin
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
api-platform/admin#616 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 64/100
api-platform/admin#660 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
api-platform/admin#659 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
api-platform/admin#631 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
api-platform/admin#626 · 1 comment · 1 reaction ·
All issues in api-platform/admin
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vicharanashala/fln#563 ·