ListGuesser keeping unusable defaults for sort and pagination regardless of support in API
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react, typescript
Research direction
Start with the ListGuesser and FieldGuesser entry points shown in the report, including the useEmbedded and perPage behavior. Check how unsupported sorting and pagination are detected or rendered, then verify that a resource without filtering or configurable pagination shows only supported controls and correct page counts.
Written by the indexing model from the issue text.
Description
API Platform version(s) affected: 2.6.2
Description
I am using useEmbedded true. Because of that I was required to setup ListGuesser for resource manually, like in docs for admin.
My API is not supporting any king of filtering, sorting or searching for now. Pagination is on default 30 items not changeable. Kind of default CRUD "entity/api resource" with nothing extended so far.
I would expect not to have offered sorting on columns and pagination under grid defaulting for 30 items, not 10 and displaying 30 recieved ones. Which results in last pages of pagination resetting to first page as they do not exist. I have 110 items and 4 pages and admin show 110 items on 11 pages available as pagination.
Possible Solution
I tried to pass perPage={30} property to ListGuesser. It is kind of working, but pagination is now only 2 arrows, forward and backward, without showing any pages number links at all.
Unusable sorting is still present.
Additional Context
const FoodList = (props) => (
<ListGuesser {...props}>
<FieldGuesser source="title" />
</ListGuesser>
);
- 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
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100