19 replies

Is it possible to disable pagination entirely for a read action?

I'm using AshGraphQL, and I have a pretty bespoke read action that through some reasonably complex logic related to some custom arguments kind of "self-paginates" - the implementation and design reasons for this are more than is worth explaining here, and yes, I wish it were different than it is and may even refactor away from this in the future, but that will take some time to do... for now, suffice to say that when generating my graphql schema, I'd really love to be able to not show the pesky

limit

limit

and

offset

offset

params in queries/relationship loads, since the bespoke logic of the action kind of already accomplishes what pagination is doing, so it's confusing for the front end devs that consume my API to see those pagination params that are functionally redundant.

I found paginate_with and paginate_relationship_with, which seem to imply that I might be able to pass

nil

nil

to disable pagination, but afaict that doesn't seem to do it. Is this something that's supported?

Solution

You'll have to add a

:none

:none

atom

Jump to solution

Ash Framework•9mo ago•

19 replies

Jesse Williams

Is it possible to disable pagination entirely for a read action?

limit

limit

and

offset

offset

nil

nil

to disable pagination, but afaict that doesn't seem to do it. Is this something that's supported?

Solution

You'll have to add a

:none

:none

atom

Jump to solution

Is it possible to disable pagination entirely for a read action?

Is it possible to disable pagination entirely for a read action?

Similar Threads

Similar Threads

Similar Threads