Niraj Kamdar

@vitalik I am using `__call__` for async `__init__` feature in my async-files library: https://github.com/Niraj-Kamdar/async-files. This may not be ideal but it's less verbose then other approach and intuitive (or atleast...

We can use [aiohttp](https://docs.aiohttp.org/en/stable/) instead of requests to make [client](https://github.com/appwrite/sdk-for-python/blob/master/appwrite/client.py#L70) module async. By doing this we can make `call` method an awaitable coroutine and this will propagate all the way...

Yes, we can make `call` method an awaitable by running it in threadpool but this solution has a con - by default, it will only run 5 tasks concurrently while...

@krisbitney default uri is the interface uri. In most cases, you'd be invoking the interface (since we assume everything is an interface: wrapper and plugin invoke are just the interface...

@dOrgJelli Can/Should we add a formatter with our own configs so that we don't get our git changes polluted by default formatter of the devs?

Closing this since moved to the python-client repo

We are using `Promise.then` at some places and since we use `async..await` semantics mostly, it looks out of place. It would be nice to stick to one pattern if possible.

@dOrgJelli I am not sure whether we want to do it this way now. Before we had recipe embedded in the meta manifest that's why when we upgraded to workflow...

Here's the hackmd: https://hackmd.io/@zgxjyig-QeyCd_p_Oc0yBQ/S14aC5Qko

I'd expand this in the ability to add schema transformations: Here are some common transformations: 1) rename field while transforming - field/type aliases for the types that can't be represented...