Sophie Dankel comments

Results 94 comments of


                                            Sophie Dankel

Using a custom deployed address to interact with written contract

@calldelegation Could you explain more about how this would work?

Using a custom deployed address to interact with written contract

We might to wait for the ABI to be deployed on chain to support this.

Executing read functions on Sway playground consumes gas

We can use `isReadOnly` now to make all read functions dry-run: https://github.com/FuelLabs/fuels-ts/pull/2008

Flaky LSP test: `go_to_definition_for_paths`

This [PR](https://github.com/FuelLabs/sway/pull/6422) failed when rerunning CI and didn't touch this part of the code at all https://github.com/FuelLabs/sway/actions/runs/10426298793/job/28878975861?pr=6422

Flaky LSP test: `go_to_definition_for_paths`

Another example: https://github.com/FuelLabs/sway/actions/runs/10781130365/job/29898407068?pr=5539

forc-crypto should be added to the nix flake

We should add `forc-debug` as well.

package-lock.json version not updated correctly

> @sdankel setting the following as a pre-commit script is working fine for me. Obviously change the ```cwd``` line to suit your needs. I have it as ```pre-commit: .github/workflows/version-pre-commit.js``` >...

feat: allow users to open sway playground for full code examples

This PR can be updated to use sharable links with the Share button: https://github.com/FuelLabs/sway-playground/issues/78 Once this is merged: https://github.com/FuelLabs/fuel-deployment-v2/pull/442

Formatter mis-formats the associated-type semicolon

Thanks for the bug report, I was able to reproduce it. The formatter should never produce different results on the second run, and the semicolon is definitely mis-formatted.

Add metadata in the preamble

This looks good! I'm wondering if it would make sense to move the existing data section offset inside of the metadata as well since conceptually it is also metadata.