-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
[docs] Added additional explanations #4059
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for doing this! There seems to be a little typo of "scenario" that should be fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, Adam! I made a few small changes in commits here and left a couple of questions in comments.
Please note, we have moved the cli-client.md file to the contribute subdirectory. So I can include your change to that file there.
doc/src/build/cli-client.md
Outdated
@@ -998,6 +998,9 @@ Please see the [Move developer documentation](move/index.md) for a | |||
description on how to [write a simple Move code package](move/write-package.md), | |||
which we can publish using Sui client's `publish` command. | |||
|
|||
> **Important:** All calls to functions in the `debug` module must be removed from no-test code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do we mean by "no-test code" here? I see no other reference on this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added additional explanation in both places.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added additional explanation in both places.
Thanks, Adam! LGTM.
@@ -21,6 +21,9 @@ debug::print_stack_trace(); | |||
``` | |||
Alternatively, any call to `abort` or assertion failure will also print the stacktrace at the point of failure. | |||
|
|||
> **Important:** All calls to functions in the `debug` module must be removed from no-test code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above. Let's make both references to "no-test code" clear.
I'm adding this to the newly moved |
Some of the missing explanations that affect user experience.