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
{{ message }}
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.
Good issue! But I think the description is a bit misleading. At the moment every clause is stateful, in the sense that there is no way to know if the state will or will not be changed except by looking at the logic for that clause (i.e., does it use set state or not).
It would be nice if the contract type or clause type was able to make that distinction.
This is a bit similar to the issue opened by @mttrbrts on emitted obligations here: #714
For the sake of argument, here is a contract which is stateful and for which getStateTypes() returns org.accordproject.cicero.contract.AccordContractState
Describe the bug
getStateTypes()
returnsorg.accordproject.cicero.contract.AccordContractState
for clause templates that do not utilize stateExpected behavior
The distinction between stateful and stateless clauses should be more clear.
The text was updated successfully, but these errors were encountered: