Improve UX around handling query strings

[chvck]

ahh, I found out my issue...it might be a bit of an edge case but I could imagine something similar being common enough and leading to someone suspecting that multi-line queries don't work: I first tested a query with: analytics "select 1" When I confirmed that worked, I used the up arrow to bring that line back, then I deleted the select 1 bit (leaving the " " ) Then I copied a multi-line query from the query workbench and tried to paste it in between the " ". This failed...it attempted to execute each line separately

semi-related...I tried running an analytics query without " " and it failed as expected, but the analytics -h doesn't say that the statement needs to be between quotes. It might be obvious (certainly I know that it is) but someone just blindly copying the query from somewhere might not realise it. Could we a) state in the help that quotes are required or better yet, b) automatically fill in quotes on the command line?

[ingenthr]

@chvck, what do we need for v1.0.0 here? do you think (b) is possible?

[ingenthr]

@RekhaDS and I talked a bit further about this and we think it could be skipped for v1.0.0. good to have if easy.

[chvck]

Part a of the second paragraph is easy enough. The rest I imagine is very non-trivial if even possible. That's going to be at the nushell level.

[ingenthr]

Let's state that the quotes are required, then move this to 1.0.1