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
This issue lists some ideas around improvements (especially performance improvements) fort he future iteration of #1503
To be released before or as part of Clarinet 3.0
Fully implement and test get-(stacksd|burn)-block-info? and get-tenure-info? especially when used in at-block. This is one of the main limitation at the moment
await simnet.initEmptySession(<RemoteDataSetting>); should take 0 or 1 argument. In remote data setting, initial_height and api_url should be optional
Further improvements
Save data to file system. Once a data is fetched, it's likely ot be reused (in future simnet session or in other unit tests), the block, marf data and metadata could be save in a file
Better http client and remote data handling
Refactor stacks-rpc-client so that it compiles to wasm, include repl/remote-data.rs in it
Bettter handling of network errors (block or sortition not found, api unavailable)
Remove the need for a npm dependencies in clarinet-sdk-wasm to perform synchronous http request
The NPM dependency sync-request was removed in favor of calling curl in a child process.
This issue lists some ideas around improvements (especially performance improvements) fort he future iteration of #1503
To be released before or as part of Clarinet 3.0
get-(stacksd|burn)-block-info?
andget-tenure-info?
especially when used inat-block
. This is one of the main limitation at the momentawait simnet.initEmptySession(<RemoteDataSetting>);
should take 0 or 1 argument. In remote data setting,initial_height
andapi_url
should be optionalFurther improvements
stacks-rpc-client
so that it compiles to wasm, includerepl/remote-data.rs
in itsync-request
was removed in favor of callingcurl
in a child process.epoch_for_height
used in indatastore
andrequirements
to remove the need for hard coded valuesThe text was updated successfully, but these errors were encountered: