houmark

I agree with @jonmifsud — the main interest for us is to have a count of the filtered query, so we can do a proper pagination and show the total...

Associating the word "impossible" for a query count in 2019 makes me cringe a bit. And more than that, it makes me wonder if selecting Amplify and all its (current)...

This got sidetracked by different ideas, but I'd like to know if we can expect total counts for at least Elasticsearch based queries soon? @undefobj `$ctx.result.hits.total` is in the resolver...

It seems like aws-amplify/amplify-cli#2600 made aws-amplify/amplify-cli#2602 happen, so here's to hoping that PR gets accepted fast.

Yeah, I first thought that PR would solve it due to the original code that was halfway baked in at the time. But that PR changed to just show the...

@kaustavghosh06 But how can I do that? I get 10 when I `limit` 10 in the query. If I `limit` 20, `total` is 20? If I am on the "last...

That was what I expected also, but this changed in the PR because it would leak data about the total results if `@auth` is filtering out results due to "access...

For us, first of all we would not have a leak because we don't have advanced access control in our models, so we would get the right amount of results,...

@faahim Nope. I dropped this integration for now with the plan to fork it in the future (and make a PR here so my fork could be dropped if accepted)...

Hey @gorkamolero, Long time, no see ;) Let's sync up!