Added support for pagination and queries in general.

[Gideilson-Lima]

Now it's possible to get all the documents from big collections and perform all query methods appwrite supports excepts search because I don't really understand what it does exactly and how it is related to indexes.

[pooranjoyb]

Ohh my Gawd ://

[pooranjoyb]

Awesome, dude :)
Appreciate the fact that you actually didn't miss anything, just pure buttery code.

[Gideilson-Lima]

Awesome, dude :) Appreciate the fact that you actually didn't miss anything, just pure buttery code.

Thanks for creating this SDK and allowing me to contribute in some way :)

[pooranjoyb]

Thanks for creating this SDK and allowing me to contribute in some way :)

You are welcome to contribute more. We'll be glad <3

[Gideilson-Lima]

Hey man. Our Query class is not compatible with appwrite 1.7 because they changed the request format.
In version 1.6 it was simply an escaped json string that we would append to the GET method like this:
queries[]={\"method\":\"equal\",\"attribute\":\"title\",\"values\":[\"Avatar\"]}

but now in version 1.7, it requires a URL encoded string like:
queries[]=%7B%22method%22%3A%22equal%22%2C%22attribute%22%3A%22title%22%2C%22values%22%3A%5B%22Avatar%22%5D%7D

In my personal project I simply hardcoded again replacing the old request style and it's working fine, but what do you suggest? Should we keep 1.6 queries format or totally replace it for this new one?

P.S. Personally I don't understand why they did this. Everytime we have square brackets "[ ]" in the query we now replace for %5B %5D but in the beginning of the string they kept the square brackets queries[] for some reason.

[pooranjoyb]

In my personal project I simply hardcoded again replacing the old request style and it's working fine, but what do you suggest? Should we keep 1.6 queries format or totally replace it for this new one?

I think it's better if we go on with the stable 1.6.x version as of now. coz this minor change could bring up many discrepancies in the queries.