Nedim Salkić
Nedim Salkić
Blocked by: - #1356 That PR already has documentation that this issue requests and it might be enough. I'll reevaluate once it's merged.
Resolved in https://github.com/FuelLabs/fuels-ts/pull/1356.
I asked @FuelLabs/client the following question: > The graphql API returns an errors array when an error happens on the VM. In practice, are there cases where the VM will...
> Speaking of all errors, do we have a unified list of possible errors the VM can throw, or how else should we know when we mapped them all? I...
Those errors look like graphql-related errors thrown when writing custom queries. The SDK itself internally should never encounter them because we use `Provider.operations`, which is type safe because it's generated...
@arboleya That's a good point and I agree with it. I'll close the issue.
@danielbate as @petertonysmith94 said, this wasn't completed. Having to pass the bytecode as config was the thing blocking it and #2824 resolved that. I will reopen it.
The `options` property is rarely used even in our own tests - maybe nowhere except `launch-test-node.test.ts` - so making the default simpler is a win in my book.
I wholeheartedly agree with the direction. I think we could give the users the full factory and have them do whatever they want with it: ```ts // counter-factory.ts import {...
Yes, please create a PR for this if you want.