Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Promises basics#3285

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.

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

Already on GitHub?Sign in to your account

Open
bogdanbacosca wants to merge4 commits intojavascript-tutorial:master
base:master
Choose a base branch
Loading
frombogdanbacosca:promises-basics-en

Conversation

bogdanbacosca
Copy link
Contributor

Lines 294 and 327 refer to line 84:

A promise that is either resolved or rejected is called "settled"

Lines 227 and 225 just have some potentially good improvements for readability.

"also" or something equivalent would be a good continuation of the "Just like" starting point from the beginning of the sentence. (maybe)
The addition of the word "if" would probably make more sense.
Replaced resolved with settled for consistency.
switched 'resolves' with 'settles' for consistency
@bogdanbacoscabogdanbacosca changed the titlePromises basics enPromises basicsNov 29, 2022
Copy link
Contributor

@shallow-beachshallow-beach left a comment
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

a few comments


The call `.finally(f)` is similar to `.then(f, f)` in the sense that `f` runs always, when the promise is settled: be it resolve or reject.

The idea of `finally` is to set up a handler for performing cleanup/finalizing after the previous operations are complete.

E.g. stopping loading indicators, closing no longer needed connections, etc.

Think of it as a party finisher. No matterwas a party good or bad, how many friends were in it, we still need (or at least should) do a cleanup after it.
Think of it as a party finisher. No matterif a party was good or bad, how many friends were in it, we still need (or at least should) do a cleanup after it.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

i prefer the solution at#3390

@@ -214,15 +214,15 @@ The call `.catch(f)` is a complete analog of `.then(null, f)`, it's just a short

## Cleanup: finally

Just like there's a `finally` clause in a regular `try {...} catch {...}`, there's `finally` in promises.
Just like there's a `finally` clause in a regular `try {...} catch {...}`, there'sa`finally` in promises also.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

maybe:

Just like there's afinally clause in a regulartry {...} catch {...}, there's afinally for promise chains.

@@ -291,7 +291,7 @@ Sometimes, it might be that a promise is already settled when we add a handler t
In such case, these handlers just run immediately:

```js run
// the promise becomesresolved immediately upon creation
// the promise becomessettled immediately upon creation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

disagree, 'resolve' goes well with use ofresolve in the article's examples. Maybe 'fulfilled' if trying to use ECMA term.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@shallow-beachshallow-beachshallow-beach left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@bogdanbacosca@shallow-beach

[8]ページ先頭

©2009-2025 Movatter.jp