This message was deleted.
# typescripts
sparse-intern-71089
11/12/2021, 3:05 PMThis message was deleted.
m
magnificent-lifeguard-15082
11/12/2021, 3:08 PMFound this thread, nvm. https://pulumi-community.slack.com/archives/CJ909TL6P/p1635891817067700
magnificent-lifeguard-15082
11/12/2021, 3:09 PMWould a PR be reasonable to allow for a generic version of
ComponentResource<pulumi.Outputs>magnificent-lifeguard-15082
11/12/2021, 3:11 PMThere’s a problem with having to add class property types because typescript will complain that the property is “definitely not set in the constructor”.
magnificent-lifeguard-15082
11/12/2021, 3:12 PMUnless you have to also set the property yourself (I was expecting registerOutputs to do this)
m
miniature-king-36473
11/12/2021, 5:19 PMIn a pulumi component you do all the work in the constructor, so there is not usually an issue with setting the properties there?
miniature-king-36473
11/12/2021, 5:20 PMyes - you set the properties of the class yourself - in the same way you would for other typescript classes - there is no magic going on with register outputs...
m
magnificent-lifeguard-15082
11/12/2021, 6:28 PMIf there's no magic what does it do? My expectation was that it (registerOutputs) would be required so that pulumi could correctly understand the dependency graph. But then if it's doing that, why not set the properties too so I am not having to jump to three places to set an output which is highly error prone (property type, set the property in constructor, call registerOutputs)?
Eg. with psuedo:
Integration { target = myFunctionComponent.lambdaArn }