Document possible values of analytics command #15039
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jbogarthyde
added
area: @angular/cli
effort1: easy (hours)
freq1: low
|
I need information about the "ci" value - how does it affect behavior? |
alan-agius4
approved these changes
Jul 15, 2019
mgechev
pushed a commit
that referenced
this pull request
Jul 15, 2019
* docs: add possible values to ref doc for analytics command * docs: add ci value
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The possible values are in the JSON (and an error message) but are not mentioned in the doc.
This is probably true of all enum values - in the standard API doc, value types are automatically extracted into the doc, but since these are always strings, we don't do that. We should have a way to automatically include enumerated value descriptions, that would go into the arg description.
For now, I've put them into a long-description for the command.