[docs] - document that asset outputs work the same as op outputs

[sryza]

What's the issue or suggestion?

all the patterns described here - link to https://docs.dagster.io/concepts/ops-jobs-graphs/ops#outputs- apply to @asset- decorated functions as well

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[erinkcochran87]

A few thoughts after looking at this a bit more:

• It seems odd to talk about outputs without also talking about inputs
• After looking at the API docs for assets and ops, it's a bit unclear to me how this is a 1:1 between assets and ops. Ex: While there are ins and outs parameters for both concepts, the descriptions here make them seem like they're fundamentally different from each other.

This won't be addressed in time for the release this week. Next steps are to sync up with someone to talk through this.

[sryza]

The particular bits that are documented on ops but also apply to assets are these:

• "Return type annotations can be used directly on ops. For a single output, the return annotation will be used directly for type checking."
• "If there are multiple outputs, a tuple annotation can be specified. Each inner type of the tuple annotation should correspond to an output in the op."
• "Outputs are expected to follow the order they are specified in the op's out dictionary. In the above example, the int output corresponds to int_output, and the str output corresponds to str_output."
• "Note that if you would like to specify a single tuple output and still utilize type annotations, this can be done by providing either a single Out to the op, or none."

From https://docs.dagster.io/concepts/ops-jobs-graphs/ops#outputs.