Anderson Arboleya

@xgreenx Great point! Client cache is under the user's control since their app will be hosted by themselves, and the browser should cache things automatically following whatever configurations they have...

@nedsalk The first approach is similar to what I suggested, but without the server involved, and should also work. The second one, however, could be [disastrous](https://medium.com/arthera/ledger-connectkit-connector-incident-c85e0a56b6b2).

Since we expect the data to satisfy the `InputData[]` shape, I can't see how it could be a non-array. Unless we'd define it as `InputData | InputData[]`, it all depends...

I wonder if https://github.com/FuelLabs/fuels-ts/pull/1867 wouldn't also close this issue. > _cc @petertonysmith94_

This is not recommended, so I'd say _almost_ never.

@jindw I don't really know exactly what's the point being discussed here, but perhaps this article may be of help. http://johndyer.name/native-browser-get-set-properties-in-javascript/

@nedsalk Exactly. 👌 @Dhaiwat10 The idea is to validate that conditionals, prompts, and warnings/errors are all working correctly. The coverage report can help you understand the parts of the code...

Like this one? [.github/workflows/md-lint.yaml](https://github.com/FuelLabs/fuels-ts/blob/master/.github/workflows/md-lint.yaml) cc @Dhaiwat10

Relevant places to change should involve the ones included in these commits: - https://github.com/FuelLabs/fuels-ts/pull/2045/commits/47c511eb3fe19e7cd1b39f0948649cd47f4c3e0a - https://github.com/FuelLabs/fuels-ts/pull/2045/commits/be3accd9594a4b2be5d061fbfdf0b8451d802cb2

Blocked: - Needs final Testnet URL