You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
While exploring and interacting with the Sway playground, I found an issue while reading the state. To take the example of the default contract (counter). After compiling and deploying the contract, during the interaction, calling the get function requires gas to get the current state of the counter. I assume, all the function components are mapped to the same read-write functionality whereas it should be differentiated as read & read-write. Also, read functions don’t require a dry run as it will just return the current state.
The text was updated successfully, but these errors were encountered:
https://forum.fuel.network/t/executing-read-functions-on-sway-playground-consumes-gas/4914
Hi,
While exploring and interacting with the Sway playground, I found an issue while reading the state. To take the example of the default contract (counter). After compiling and deploying the contract, during the interaction, calling the get function requires gas to get the current state of the counter. I assume, all the function components are mapped to the same read-write functionality whereas it should be differentiated as read & read-write. Also, read functions don’t require a dry run as it will just return the current state.
The text was updated successfully, but these errors were encountered: