Unable to use "distinct" parameter about clever-python HOT 4 CLOSED

The first error is happening because we add page parameters to all requests from all. Because we paginate automatically, we disallow sending limit and page, which causes the second error.

Not sure if there should be a special case for distinct in these functions, or if distinct should be broken out into its own method, a.la. clever.Section.distinct("period").

I think from a readability/code complexity point of view, the second one is probably better (and I would lean towards that), but you could also make an argument that the smaller the API profile, the better (e.g. currently we only have two methods: iter and all).

from clever-python.

@azylman why doesn't distinct allow pagination?

from clever-python.

@dccarroll - Interesting catch - I didn't realize these were interdependent when we hardcoded limit for pagination purposes.

limit implies two things (1) MAX results to return (2) PAGE_SIZE. I suggest that clever-python hides (2) from the library consumer. (1) seems a much more sensible way of thinking about it from the library's perspective.

I don't like adding another method either; however, we might consider that the parameters need not exactly map to the API. as we do with all(), there could be more abstraction between the goal (fetching distinct items) and exactly what query parameters get passed behind the scenes to the API.

from clever-python.

No idea, I just know the API rejects any query parameters with distinct except where and limit.

Maybe the aggregation pipeline (which we use for distinct) doesn't offsets?

from clever-python.