mirror of
https://github.com/nushell/nushell
synced 2024-12-26 13:03:07 +00:00
f37f29b441
* start playing with ways to use the uniq command * WIP * Got uniq working, but still need to figure out args issue and add tests * Add some tests for uniq * fmt * remove commented out code * Add documentation and some additional tests showing uniq values and rows. Also removed args TODO * add changes that didn't get committed * whoops, I didn't save the docs correctly... * fmt * Add a test for uniq with nested json * Add another test * Fix unique-ness when json keys are out of order and make the test json more complicated |
||
|---|---|---|
| .. | ||
| add.md | ||
| append.md | ||
| average.md | ||
| cd.md | ||
| compact.md | ||
| config.md | ||
| count.md | ||
| date.md | ||
| default.md | ||
| echo.md | ||
| edit.md | ||
| enter.md | ||
| env.md | ||
| exit.md | ||
| fetch.md | ||
| first.md | ||
| format.md | ||
| from-csv.md | ||
| from-json.md | ||
| from-toml.md | ||
| from-tsv.md | ||
| from-xml.md | ||
| from-yaml.md | ||
| get.md | ||
| group-by.md | ||
| help.md | ||
| histogram.md | ||
| history.md | ||
| inc.md | ||
| last.md | ||
| lines.md | ||
| nth.md | ||
| open.md | ||
| pick.md | ||
| pivot.md | ||
| prepend.md | ||
| ps.md | ||
| README.md | ||
| reject.md | ||
| reverse.md | ||
| save.md | ||
| shells.md | ||
| size.md | ||
| sort-by.md | ||
| split-column.md | ||
| split-row.md | ||
| str.md | ||
| sum.md | ||
| sys.md | ||
| tags.md | ||
| to-csv.md | ||
| to-json.md | ||
| to-toml.md | ||
| to-tsv.md | ||
| to-url.md | ||
| to-yaml.md | ||
| trim.md | ||
| uniq.rs | ||
| version.md | ||
| where.md | ||
How do I get started?
Pick any command from the checklist and write a comment acknowledging you started work.
Instructions for documenting a Nu command of your choosing
Name the file after the command, like so:
command.md
Example: If you want to add documentation for the Nu command enter, create a file named enter.md, write documentation, save it at /docs/commands/[your_command_picked].md as and create your pull request.
What kind of documentation should I write?
Anything you want that you believe it best documents the command and the way you would like to see it. Here are some of our ideas of documentation we would love to see (feel free to add yours):
- Examples of using the command (max creativity welcomed!)
- Description of the command.
- Command usage.
Anything else?
Of course! (These are drafts) so feel free to leave feedback and suggestions in the same file.
Happy Documenting.