-
Notifications
You must be signed in to change notification settings - Fork 86
Conversation
@@ -76,8 +76,7 @@ export function assertDefined<T>(a: T | undefined): T { | |||
} | |||
|
|||
export async function mapDefinedAsync<T, U>( | |||
arr: Iterable<T>, mapper: (t: T) => Promise<U | undefined>): | |||
Promise<Array<awaited U>> { | |||
arr: Iterable<T>, mapper: (t: T) => Promise<U | undefined>): Promise<U[]> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Running npm install
gave me the latest next
, rather than the one recorded in the lockfile, and it seems like awaited
was recently reverted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't figure out what paths should be allowed and disallowed versus which ones currently are allowed/disallowed. Can you give examples?
32def61
to
be2cff8
Compare
Currently these are allowed:
Whereas this is disallowed:
The above should all be allowed now, but not those with patch components:
|
I published 3.4.1 just now, so Definitely Typed's CI should get the new version next time it runs. |
Thanks! 🙏 |
Follow-up to microsoft/types-publisher#723.
This was causing CI on DT to fail for DefinitelyTyped/DefinitelyTyped#43179.
I couldn't figure out how to write a test to exercise this code-path. If it’s easy to point out, I’d gladly add test coverage.