Add note on supported value types in raw-fields#3400
Merged
Conversation
Contributor
Author
|
It would be great if someone can validate this statement is also accurate for objects. |
Contributor
|
Thank you for the contribution! This is true, we currently don't support JSON arrays or nested objects. This is not documented, but implied from the omission of said functionality. The workaround is to prepare the raw JSON payload yourself and pass it in via We plan to support JSON arrays/nested objects in the future: #1484. Because of this, I would rather not add this notice just yet, since it's going to become obsolete soon. |
mislav
suggested changes
Apr 12, 2021
Proposing a slight amendment to the `gh api` field docs to clarify the current limitation around "complex" field values, e.g. arrays/objects. Related: cli#1484 Signed-off-by: Michael Gasch <mgasch@vmware.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Proposing a slight amendment to the
gh apifield docs to clarify the current limitation around "complex" field values, e.g. arrays/objects.Related: #1484