FindAll should have parameters for skip and limit about api2go HOT 7 CLOSED

http://jsonapi.org/extending/ has an example about pagination at the bottom, it introduces after, before and limit, as alternate suggestions to skip and limit, which fixes the problem with "jumping items" on page change.

from api2go.

What do you think about passing the query parameters through to the datasource?

from api2go.

Well, they don't have to be parameters of the function. But I would provide utility functions in order to get those, if set.

What do you think?

I would love to have this as api2go feature. Maybe we can find a comfortable solution?

Something like.. SetPageLimit(25).. GetStartItem() string; GetToItem() string;

from api2go.

we could standardize the possible query parameters in my opinion. Put them all into a new struct and pass that struct as a parameter to findAll

from api2go.

I'm not sure standardizing query params makes sense. What do we provide – limit, order (desc / asc), order_col, offset, searchterm, …? These things might be highly application-dependant, so I'd say a map[string]string is the simplest and most general solution.

from api2go.

Hm yes i think you are right. Let's do it that way then.

from api2go.

yeah that sounds good.

from api2go.