fix: mutable self
required for dispatchable ink! methods
#235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our current
pop-api
contracts, we do not markself
asmutable
because the contract storage is not being modified directly; instead, the runtime storage is mutated by thepop-api
. However, on the client side, when using libraries that support ink! (such as PJS or Dedot), these methods are perceived asquery
rather thantx
, as the contract itself does not undergo changes.While it's unclear whether
pop-api
will be utilized in immutable methods in production, it is crucial to clearly state this requirement in the documentation. This will help ensure that developers understand how pop-api behaves and how it might impact the perception and execution of methods in client-side libraries.cc: @Daanvdplas @peterwht