docs: Provide more examples on client: commands and platform

[helderco]

Resolves #1890

👀 Preview

Signed-off-by: Helder Correia

[jpadams]

@helderco Love these improvements.
The only thing I'd add regarding output fields is that they have to be generated fields (or whatever best term is) instead of concrete fields, right?

Some users might be confused that they didn't get output for out1 below:

dagger.#Plan & {
    actions: {
        build: {
            out1: "hello"
            _nop: core.#Nop & {input: "helloNop"}
            out2: _nop.output
        }
    }
}

$ dagger do build
[✔] actions.build                                                           0.0s
Field  Value
out2   "helloNop"

[helderco]

Yes, but non-output fields are private in these examples, so I don't see the confusion.

[samalba]

Agreed with Helder, LGTM.

[jpadams]

Yes, but non-output fields are private in these examples, so I don't see the confusion.

I have no issues with your examples :) If folks follow them, they will do well. 👍

I mean that I don't think there is anywhere in the docs where it is stated that the output fields must be generated fields. We should say that somewhere. Why not here? :)

I can follow with a PR. I thought that since you'd been looking at these docs you might have best opinion on where to put that statement.

[helderco]

I think the proper place for that is in https://docs.dagger.io/1228/handling-outputs