-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI: inconsistencies in silent auto-restoring of expired entries #1023
Comments
Is there an equivalent to |
Bump was renamed to extend in: |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedHello 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. My background and how it can be leveragedI 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. How I plan on tackling this issueI 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. |
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.The text was updated successfully, but these errors were encountered: