Open c0linw opened 1 year ago
Is there an equivalent to soroban contract bump
now that it's removed (according to latest changes on main
)? Looks like soroban contract invoke
is still silently restoring contract entries, unless I'm mistaken.
Bump was renamed to extend in:
I am applying to this issue via OnlyDust platform.
Hello I'm a frontend and also a blockchain developer and I would love to work on this issue.
I am applying to this issue via OnlyDust platform.
I have extensive experience working with CLI tools in JavaScript, TypeScript, Go, and Rust, including contributing to open-source projects. My background in designing consistent user experiences in CLI tools, particularly in ensuring predictable and clear behavior for developers, will be valuable in addressing this issue.
I would first analyze the root cause of the silent auto-restoring behavior by examining both soroban contract invoke and soroban contract bump commands. My approach would focus on ensuring consistency across these operations. To achieve this, I would:
Determine whether to standardize the silent restore behavior for all CLI operations or remove it entirely. Update the documentation to clearly outline the behavior for each command. Implement tests to validate consistent behavior across both scenarios, ensuring developers have a clear understanding of when and why a contract is restored or needs to be bumped.
Thank you I will start right away
The CLI will silently restore contract entries when using
soroban contract invoke
, but not when usingsoroban contract bump
. This could confuse developers when they are able to call a contract that cannot be found, or make it unclear that the contract actually needs to be bumped. It may be helpful to keep the behaviour consistent across CLI operations either by adding the silent restore to all relevant operations, or by removing it.