Green Baneling
Green Baneling
Hi, I also want to participate in that discussion=) > Aaand if we decide to keep the things as they are - it's the worst solution, as namespace methods might...
> As per the rest of the API, everything is camelCase. I'll re-iterate, not going to mix interfaces and methods under a single point of the existing interface, it is...
> PITA = Pain In The Ass. Sprinkling in asserts everywhere is exactly that - and inconsistent with the API. I didn't mean to add asserts=) I meant that if...
Okay, so when the usage of the namespaces/interfaces will be popular in ink!, we can elaborate on merging `ns` into `query` and `tx`?=) > It is the second variant. The...
> Okay, so when the usage of the namespaces/interfaces will be popular in ink!, we can elaborate on merging ns into query and tx?=) For that question I need "yes"...
When do you plan to merge that change?=)
> I assume it is the gas metering then. It generates one host function call for every basic block. I think what we can learn from that is that adding...
@ra0x3 I am closing this issue because GraphQL already provides a way to fetch everything in one request=) If you need any other batch request, you can use the idea...
I want to highlight that we still plan to dry run transactions on the user side in the future, and it requires the whole `fuel-vm` that will be significantly more=)...
Added [an example](https://github.com/xgreenx/ink-env-example) to show how it could work and how it is easy to do on the developer side=)