Proposal: AsyncReturnType about type-fest HOT 10 CLOSED

What's the practical difference to #42

I think that's difference. It's just a combination of them:

Unpromise<ReturnType<typeof asyncFunction>>
ResolvedType<typeof asyncFunction>

Funny thing is that all the examples in #38 and #42 are exactly:

Unpromise<ReturnType<typeof asyncFunction>>

So perhaps ResolvedType makes more sense than a standalone Unpromise.

Also maybe it should be called AsyncReturnType instead of ResolvedType

from type-fest.

PR welcome for AsyncReturnType.

@sindresorhus Since you're accepting PRs for this, do you want me to submit one for this after PromiseValue has been merged?

from type-fest.

@resynth1943 Yes. That would be great. 🙌

from type-fest.

What's the practical difference to #42 (apart from the fact that ResolvedType is a combination of ReturnType and the proposed Unpromise)?

from type-fest.

@dylang ⬆️

from type-fest.

This is what I'm using currently:

type Unpromise<MaybePromise> = MaybePromise extends Promise<infer Type> ? Type : MaybePromise;
type AsyncReturnType<T extends (...args: any) => any> = Unpromise<ReturnType<T>>

You can probably merge the two and avoid Unpromise but I don't know how 😳

from type-fest.

I still think Unpromise makes sense as an independent building block.

PR welcome for AsyncReturnType.

from type-fest.

Relevant TypeScript issue: microsoft/TypeScript#28105

from type-fest.

@sindresorhus I think that's more about Unpromise and AsyncReturnType

A PR for that issue has been opened: microsoft/TypeScript#35998

from type-fest.

Gotcha. When you get a chance, @sindresorhus, could you check out #75?

from type-fest.