Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Part2: Promise lingo and states vs fates #2356

Open
outbits opened this issue Nov 17, 2022 · 1 comment
Open

Part2: Promise lingo and states vs fates #2356

outbits opened this issue Nov 17, 2022 · 1 comment

Comments

@outbits
Copy link

outbits commented Nov 17, 2022 •
edited
Loading

Hello!

I noticed in part2 that the material could have been conflating states and fates of promises:
image

This could potentially trip people up down the line (It has been the case for me certainly, for some time, that's why I'm posting this), because rejected promises can also be unresolved, or resolved to a value or another promise. .

Maybe rewording things a bit, or redirecting to the fates and states document in the original Promises proposal for more info is worthwhile?
@KartikDotDev
Copy link
Contributor

Hey, This would be updated and fixed with a PR, this seems like a valuable addition to make.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@outbits @KartikDotDev