-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forc deploy
should accept initial storage slots
#2010
Comments
With #2078, |
Having that feature probably doesn't hurt. |
Just to clarify, |
## Description Closes #2010 Notes: - I couldn't use `from_reader` to deserialize the file contents due to this issue: FuelLabs/fuel-vm#643 ## Checklist - [x] I have linked to any relevant issues. - [ ] I have commented my code, particularly in hard-to-understand areas. - [ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [ ] I have added tests that prove my fix is effective or that my feature works. - [ ] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [ ] 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). - [ ] I have requested a review from the relevant team or maintainers.
forc deploy
should accept initial storage slots, likely through a JSON file that contains: https://github.com/FuelLabs/fuel-specs/blob/master/specs/protocol/storage_initialization.md. The compiler will emit this file for every contract.It should also accept initial state for configurables.
The text was updated successfully, but these errors were encountered: