-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug][Grid] Unable to disable pagination #27
Comments
Thank you for a hint, @vvasiloi |
@vvasiloi Tried that, with no success. I think that the reason is described here: Sylius/SyliusResourceBundle@9d0a62f#diff-65e50375d85391f98eb10c4d1edaa144R90 and it have sense from that point of view (deny to load 1 000 000 records per time to not break server), but from other side, after that change, there are no chance to create not limited list - we only can limit it to some big amount, like 1000 at grid which will be not what we expect if we will have 1001+ records... And if so, we should change docs:
Providing |
@igormukhingmailcom So the constraint is in the Resource Bundle and not in Grid Bundle? |
Looks like the Grid Bundle is not using the limits at all. |
There is a workaround: |
Sylius version affected: 1.6 (at least since 1.4 affected)
Description
Here in docs we can see that:
But that's not true. It passing tests (
it_has_no_pagination_limits_by_default
) that checks it should be without pagination by default, but in fact, even we passlimits: []
it replaced by defaults fromConfiguration.php
I guess...TLDR
Tried:
limits: ~
limits: null
limits: []
with no success.
It can be only array as I can see here.
And as far as option have default value,
ArrayToDefinitionConverter
always see key exists so pagination is always active.Steps to reproduce
Define your grid with
limits: ~
or any of tried definitions and see that pagination still exists.Possible Solution
Not sure...
But expecting support of
[]
andifTrue(is_array(..) && is_empty(..))
->thenUnset
...And probably
treatFalseLike([])
...Workaround for devs who faced issue until it fixed
Something like:
The text was updated successfully, but these errors were encountered: