Closed BlaineHeffron closed 1 month ago
Still marked as draft. Is that intended, @BlaineHeffron? Seems like it's about ready to go!
Still marked as draft. Is that intended, @BlaineHeffron? Seems like it's about ready to go!
See my comment here - https://github.com/stellar/js-stellar-sdk/pull/960#discussion_r1595553929
To summarize, I think it makes sense since we are giving a way to create it from a wasm we should also give a way to create it from a wasmHash. This would also make sense in the context of our e2e tests.
Should be all ready to go now.
Latest commit fixes all of Chad's comments.
Tests are failing
Tests are failing
Looks like that weird spawnSync issue we were seeing before. I added a fallback in case it doesnt work the first time.
ok, I guess I just don't have the correct permissions to get this thing marked as mergeable
I addressed comments from @Shaptic although this now is dependent on https://github.com/stellar/js-stellar-base/pull/744 being merged first. The latest changes remove the external js-xdr dependency and uses the ceareal
namespace from stellar-base
for XdrReader
.
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
Package | New capabilities | Transitives | Size | Publisher |
---|---|---|---|---|
npm/@stellar/stellar-base@12.0.0-rc.1 | None | +3 |
711 kB |
🚮 Removed packages: npm/@stellar/stellar-base@11.1.0
Adds a
from
method which uses thecontractId
to create an instance of theContractClient
by retrieving the wasm from the blockchain and extracting itsContractSpec
. I also add afromWasm
method which bypasses the wasm retrieval portion if you already have the wasm buffer.