https://pulumi.com
Join Slack
This message was deleted.
# typescript
s
This message was deleted.
m
Would a PR be reasonable to allow for a generic version of 
ComponentResource<pulumi.Outputs>
which provides type safety for registerOutputs and types the class properties?
There’s a problem with having to add class property types because typescript will complain that the property is “definitely not set in the constructor”.
Unless you have to also set the property yourself (I was expecting registerOutputs to do this)
m
In a pulumi component you do all the work in the constructor, so there is not usually an issue with setting the properties there?
yes - 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
If 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 }
should allow pulumi to say "Integration depends on myFunctionComponent" and not "integration depends on a lambda resource" which is supposed to be hidden and encapsulated in the component.
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by