The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

it seems like users aren't expected to supply explicit typing for the injected context argument -- what's the rationale there?

just not intending that to be a published/supported api at this time?

feels like a gap given the level of typing throughout the user experience otherwise
(and I have a lint rule that asks for types on each argument).

(deleting previous message)

`SystemComputeExecutionContext` is available to import from `dagster` and you should be able to use it to type the context argument

not proud of the name, should probably be nicer for end user consumption. Consider giving it a type alias.

We could definitely document this better

I use `ComputeExecutionContext` for solids and `InitResourceContext` for resources. I thought `SystemComputeExecutionContext` was internal.

^ this is actually right - ill put up a diff to properly expose it at the root of `dagster` and cite it in the docs

could we alias these as `SolidContext` and `ResourceContext`

workin on a diff max we can discuss it there