-
Notifications
You must be signed in to change notification settings - Fork 56
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
Migrate all the docs to use near-cli-rs instead of JS version #235
Labels
documentation
Improvements or additions to documentation
Comments
Closed
@elliotBraem Sure, consider submitting the PR to the docs ;-) |
@frol Thank you for the description of migration cli. I have started to dive into NEAR, and this path is not described. |
bucanero
added a commit
to near/docs
that referenced
this issue
Jan 17, 2024
* Update "Building Smart Contracts" Quickstart to use near-cli-rs Now uses near-cli-rs (near/near-cli-rs#235) --------- Co-authored-by: Damián Parrino <bucanero@users.noreply.github.com> Co-authored-by: gagdiez <gagdiez.c@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a massive effort, but it will be a quality of life improvement for many!
There is already a great start here: https://docs.near.org/tools/near-cli-rs (note, all the pages on docs.near.org have "Edit this page" at the bottom, so feel free to use them)
We still lack a couple of features in
cargo-near
to replace JS version with new CLIs, but even without that we can already replace all the featured commands with pure near.cli.rs!https://docs.near.org/develop/deploy
dev-deploy
will be resolved withcargo near deploy
, but since we are not there yet:Most of the other commands will be automatically suggested to when you just run them as-is with near.cli.rs installed instead of JS CLI. So take these commands: https://docs.near.org/develop/lock
So those who will update the commands in the docs could just run them and copy the new commands from their terminal as it is suggested, and replace it in the docs.
The text was updated successfully, but these errors were encountered: