-
Notifications
You must be signed in to change notification settings - Fork 517
Describe difference between get
and select
#1744
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,33 @@ | ||
# Understanding the difference between `get` and `select` | ||
|
||
TODO | ||
### Get | ||
|
||
Extract data using a cell path. | ||
|
||
This is equivalent to using the cell path access syntax: `$env.OS` is the same as `$env | get OS`. | ||
|
||
If multiple cell paths are given, this will produce a list of values. | ||
|
||
```nu | ||
'{"name":"Alice","job":"Engineer"}' | ||
| from json | ||
| get name | ||
| describe | ||
# => string | ||
``` | ||
|
||
### Select | ||
|
||
Select only these columns or rows from the input. Opposite of `reject`. | ||
|
||
This differs from `get` in that, rather than accessing the given value in the data structure, it removes all non-selected values from the structure. | ||
|
||
Hence, using `select` on a table will produce a table, a list will produce a list, and a record will produce a record. | ||
|
||
```nu | ||
'{"name":"Alice","job":"Engineer"}' | ||
| from json | ||
| select name | ||
| describe | ||
# => record<name: string> | ||
``` |
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.
Uh oh!
There was an error while loading. Please reload 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.
This statement is a little confusing. I always thought of
get
andselect
like this.get
gets the value out of the structure it is inselect
selects the value maintaining the structure it is inI'm not saying you have to use my words, but it would be better to say it a little differently than it currently is here.
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.
That makes sense. I just grabbed the language from the implementation,
scope commands | where name == select | get extra_description.0
. I didn't realize it was already documented in the Book, so I will close this PR.