Add storage slot initialization for contract deployment #1117
Assignees
Labels
enhancement
New feature or request
Comments
This was referenced Aug 30, 2023
IGI-111
pushed a commit
to FuelLabs/sway
that referenced
this issue
Aug 30, 2023
## Description - Bumps the test harness for the [quickstart](https://github.com/FuelLabs/fuel-docs/blob/master/src/quickstart/smart-contract.md) to match beta-4 - Adds [changes ](FuelLabs/fuel-docs#102) suggested by @segfault-magnet for storage initialization on rust sdk testing. Due to the sdk storage initialization issue [fuels-rs/issues/111](FuelLabs/fuels-rs#1117) ## Checklist - [x] I have linked to any relevant issues. - [ ] I have commented my code, particularly in hard-to-understand areas. - [x] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [x] I have added tests that prove my fix is effective or that my feature works. - [x] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [x] I have done my best to ensure that my PR adheres to [the Fuel Labs Code Review Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md). - [x] I have requested a review from the relevant team or maintainers.
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As seen in sway/4634
Storage initialization values won't be automatically set by the sdk since the initialization values are output into a separate json file from the abi.
The sdk should automatically include storage slots. Otherwise, an additional config step is required to deploy the contract as seen here.
This is the fix for the same issue on fuels-ts.
The text was updated successfully, but these errors were encountered: