Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

[docs] Suggestions for cleos set account command #9476

Open
lparisc opened this issue Sep 8, 2020 · 0 comments
Open

[docs] Suggestions for cleos set account command #9476

lparisc opened this issue Sep 8, 2020 · 0 comments
Assignees
Labels
documentation Requires attention from documentation team. e.g. documentation is expected to be generated. staging doc-related issue has been resolved in merged PR. moved to staging phase for production testing.

Comments

@lparisc
Copy link
Contributor

lparisc commented Sep 8, 2020

File: docs/02_cleos/03_command-reference/set/set-account.md

Refer users to the Accounts and Permissions protocol document to give them access to the deep descriptions of perms and auths.

File: docs/02_cleos/03_command-reference/set/set-account.md#command

Remove inaccurate comment "The set account permission command is subject to change so its associated Class is not fully documented." What is subject to change are the actual fields within the JSON input. However, this is true for all commands that pass JSON input that depend on the underlying associated class. It is probably a good idea to add a blue information callout to highlight this fact on all cleos commands that receive/pass JSON parameters to the corresponding RPC API.

@lparisc lparisc added the documentation Requires attention from documentation team. e.g. documentation is expected to be generated. label Sep 8, 2020
@lparisc lparisc self-assigned this Sep 8, 2020
@lparisc lparisc added the staging doc-related issue has been resolved in merged PR. moved to staging phase for production testing. label Oct 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Requires attention from documentation team. e.g. documentation is expected to be generated. staging doc-related issue has been resolved in merged PR. moved to staging phase for production testing.
Projects
None yet
Development

No branches or pull requests

1 participant