https://dagster.io/ logo
t

Travis Cline

03/17/2020, 5:50 PM
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).
a

alex

03/17/2020, 6:05 PM
(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
c

Cagatay K

03/17/2020, 6:46 PM
I use
ComputeExecutionContext
for solids and
InitResourceContext
for resources. I thought
SystemComputeExecutionContext
was internal.
👍 1
a

alex

03/17/2020, 6:50 PM
^ this is actually right - ill put up a diff to properly expose it at the root of
dagster
and cite it in the docs
m

max

03/17/2020, 6:53 PM
could we alias these as
SolidContext
and
ResourceContext
a

alex

03/17/2020, 7:00 PM
workin on a diff max we can discuss it there
t

Travis Cline

03/17/2020, 8:19 PM
great thanks!