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.

Pulumi Community

First off, what do these translate to?
```    resolveResult!: (v: any) =&gt; void;
    rejectResult!: (e: Error) =&gt; void;```

I think  this should be similar to defining `Func&lt;object, void&gt; resolveResult`

I’m guessing you’re looking at this from the automation API perspective though? In which case, I assume you’ll have something that results in a `Task` and then needing to handle the success/failure of that task. /cc <@UQ8K13T7X>

Very close, it's `Action&lt;object&gt;` .

Ah, sorry :slightly_smiling_face: Been a while since I’ve done much C#

Next question: `resolveResult` &amp; `rejectResult` (seen <https://github.com/pulumi/pulumi/blob/master/sdk/nodejs/x/automation/server.ts#L42-L45|here>) are just declarations, right? Where are they initialized?

that chunk you linked does initialize `resolveResult` and `rejectResult` (the promise constructor runs the executor immediately <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/Promise#Parameters>)

The goal of linking these properties from the `LanguageServer.result` property was to make it easy for other downstream consumers to interact with language server. In practice we don't really use the exposed promise and handle the lifetime a little more manually.

I would not feel constrained by this for the dotnet implementation, it's really just to make callbacks easier to manage in javascript.

I’m not sure about the context but TaskCompletionSource sounds the closest to the resolve/reject pair?

I guess I should understand the context before giving advice  :joy: