Conversation
| npm access restricted [<package>] | ||
|
|
||
| npm access grant <read-only|read-write> <scope:team> [<package>] | ||
| npm access grant read-only|read-write <scope:team> [<package>] |
There was a problem hiding this comment.
why not? without the angle brackets it might be confused for being pipes.
There was a problem hiding this comment.
No, | should never mean pipe in SYNOPSIS section of manuals or on-line usage message.
Could I understand the < character as the read-open-redirect operator in UNIX shell?
There was a problem hiding this comment.
However this change could make the 'or' items be misleading, so please also consider followings:
npm access grant {read-only|read-write} <scope:team> [<package>]
or
npm access grant (read-only|read-write) <scope:team> [<package>]
darcyclarke
added
the
Priority Backlog
darcyclarke
added
Release 6.x
|
@Low-power appreciate the contribution but we're trying to limit the churn on the |
3 participants
<>should not be used for words that intent to use 'as is'.Also fixed the on-line usage string of subcommand
npm ping.