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
Contract.newFrom({ path: "0.0.X" }) and Contract.newFrom({ path: FileId.fromString("0.0.X") }
Note: the challenge here is that, since you need an ApiSession to retrieve the actual file content, that won't be immediately available on the Contract itself so we would end up deferring it.
In both of the above cases, when deploy-ing the contract to make it live, we would have to make sure to not double-create the File that the contract's bytecode depends on.
Given an existing contract's
bytecode
hosted at aFileId
, we should allow the deployment of a newLiveContract
through thatFileId
.This one is near and dear to @victorholo's heart. We just hope to get the API right.
The text was updated successfully, but these errors were encountered: