#Nushell SDK by henkhofs · Pull Request #...
1 messages · Page 1 of 1 (latest)
That's interesting. I didn't know about Nushell. In some way it looks close to dagger shell with | syntax
container from "alpine:latest"
| container with-directory "/mnt" $directory_arg
| container with-workdir "/mnt"
| container with-exec ["grep", "-R", $pattern, "."]
| container stdout
Why do you have to repeat container? my immediate gut feeling would be something's wrong here, but I can be completely wrong.
Without to know nu I would have wrote like:
container from "alpine:latest"
| with-directory "/mnt" $directory_arg
| with-workdir "/mnt"
| with-exec ["grep", "-R", $pattern, "."]
| stdout
container from "alpine" should return a Container object. Then with-directory should be called on the returned object, no from the container that is a top level command exposed by dagger returning an empty container, no?
Also, why it is container from and not container | from?
This is how idiomatic nushell looks like. See https://www.nushell.sh/commands/docs/str.html for str commands for example
A new type of shell.
I like the data capabilities of nushell
That combined with dagger is going to be awesome, it does look a bit like dagger shell, but it's more powerful with data.
I've come to use nushell as replacement for python, bash and javascript in most of my pipelines
The piping of commands feels very natural
i've updated the PR lots of improvements and also added an implementation_gaps documents, perhaps somebody would like to review that and think along 🙂