Missing documentation content

[th-schall]

I have discovered nu shell some weeks ago and have switched quickly so that it is now my standard shell on Windows and the default profile in Windows Terminal. However, there are some issues I perceive with the documentation. Maybe some or all are to blame to the fact that I am not that familiar with nu shell and its documentation yet. I present all topics anyway, so that this maybe can be resolved by just providing some remark or link.

1. I assume there are functionalites present in nu shell about which I have not found out anything yet. I cannot tell how to use this at the moment:

• database queries with parameters to make them reusable in a safe and standardized way like SQLite supports it
• interval formatting basically just like datetime formatting

2. A cheat sheet type page which is a command listing/reference organized by topic/usage area. I attached a Markdown link list sketching the idea. I use this link list for myself regularly.
   nu Shell Cheat Sheet.md

3. A scripting guide showing best practies and how to create complete non-trivial working scripts using specific tasks like these (among others):

• iterating a table and using the values in an internal or external command
• best practice way to write a readable table definitions with non-minimal data contents
• persisting (configuration) data: reading and writing useful content to text/json/xml files etc.
• best practice for using script parameters and their validation etc., like: should I check the existence of a path inside the main command block or outside?
• best practices for multi-step file and folder operations: creating a folder with a dynamic name and then creating files with dynamic content and name in the new folder etc.
• datetime arithmetics with datetimes alone, but also with datetimes and intervals for questions like five days before or how long between two timestamps etc.
• script logging best practices incl. tee-ing the log lines, maybe based on records

I figure the cookbook wants to address questions like these to some degree, but for my way of thinking the solutions there are too small, isolated without a context of using them in a script. I would look for something more comprehensive. For illustration I attached the very first two scripts I wrote for nu shell as a zip file.
script.zip

[fdncred]

I guess this is our cheat sheet https://www.nushell.sh/book/command_reference.html

[th-schall]

I know this list and I use it, but it is not that useful for newbies. You have to know quite specifically, what you are looking for and there is almost no way to identify related commands except for searching for some terms in the text. However, if you are searching for a term uncommon in the nu shell context you probably find nothing. This can happen easily, especially in these cases where nu shell names stuff differently than other shells. So yeah, the basics are there, but I see too little assistance in reaching some decent mastery of nu shell. I wanted to share this perception. Probably just my view, so if you cannot relate to it, just close the issue.

[fdncred]

I know this list and I use it, but it is not that useful for newbies. You have to know quite specifically, what you are looking for and there is almost no way to identify related commands except for searching for some terms in the text. However, if you are searching for a term uncommon in the nu shell context you probably find nothing. This can happen easily, especially in these cases where nu shell names stuff differently than other shells. So yeah, the basics are there, but I see too little assistance in reaching some decent mastery of nu shell. I wanted to share this perception. Probably just my view, so if you cannot relate to it, just close the issue.

I tend to agree with most of this.

I like your cheat sheet. I can see that being a page in the book.

[Kissaki]

Is there anything actionable regarding this? What's [still] open? What would be welcomed/accepted?

[th-schall]

I have no expectations any more at the moment with regard to my original post. Still using the documentation when I need to look anything up though I created my own solutions for recurring requirements by now.
Thanks for asking. For my concern this issue could be closed.