Nedim Salkić
Nedim Salkić
> On the docs level, I've put up some suggestions here: The suggestions were awesome! I updated the PR you created and merged it in https://github.com/FuelLabs/fuels-ts/pull/1356/commits/b9f950ea4bd877a2e994e8de3a2b6085a3e19fe8. > On a high...
@arboleya I like that, makes sense. I made the changes in https://github.com/FuelLabs/fuels-ts/pull/1356/commits/fd4f2c5cc1f3cbd5b914de19d304592c7cb7624a.
> @nedsalk will this be resolved by https://github.com/FuelLabs/fuels-ts/issues/1918? @petertonysmith94 Yes, it should be resolved alongside that issue. > I could create a options page for the Provider, akin to the...
Do you mean that we write resolvers such that e.g. a call to `provider.operations.getCoinsToSpend` would give the same result as the current `provider.getCoinsToSpend`?
The only way to go forward with this is to have an adapter between what is returned from the node and what is given to the users. We can take...
Here's a bit of a different take but in the same spirit of reducing noise: - There are no groupings by patch|minor|major because the title of the changelog already contains...
We can differentiate between breaking and non-breaking changes with $\color{red}{\bf{(!)}}$, put the breaking changes first and simplify it further: # Release - 0.43.1 ### Features - [#1826](https://github.com/FuelLabs/fuels-ts/pull/1826) Improve `Predicate` DX;...
> I see value in grouping all breaks You're right. I'll be implementing your version in the PR.
@Braqzen Thanks for the idea, it led me to #1356 which introduces everything you requested.
@arboleya we can, but I'd do it in a separate PR that can be based off of the "new ABI format" one. Also, I believe that this can bring about...