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
Somehow we dropped a method on the Zoe service API, which should have been: zoe.getInstallationRecord(installationHandle) or zoe.getInstallation(installationHandle). This would return the installation code. This solution would require two calls to get the source code, but I would expect that most of the time, there's no need to look at the source code, since most contracts are reused quite a bit and the only comparison that needs to be made is whether it is an installationHandle you recognize. Let's talk about this more in the design discussion though.
It's tested in an existing large test by checking for specific text in
the source code. We could check something less fragile (e.g. starts
with 'function getExport'), and still be pretty sure that if a string
is returned, it would continue to be the source of the contract.
fixes#877
It's tested in an existing large test by checking for specific text in
the source code. We could check something less fragile (e.g. starts
with 'function getExport'), and still be pretty sure that if a string
is returned, it would continue to be the source of the contract.
fixes#877
invite
payment amount, i can extract theinstanceHandle
zoe.getInstance(instanceHandle)
which gives me theinstallationHandle
But from the
installationHandle
, it's not clear to me how a user can get the contract source codeIn any case, going through 2 handles to get to the source code feels like too much for no good reason
Could the source code be made available directly as part of the instanceRecord?
The text was updated successfully, but these errors were encountered: