8000 Confusing language when discussing chaining after .catch · Issue #8 · info343/book · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Confusing language when discussing chaining after .catch #8
Open
@joncady

Description

@joncady

When working on problem set 6, a student tried referencing the book about promises after the a .catch, but was confused in this statement:
The .catch() function also returns a Promise, so you can continue to chain .then() calls after it. These later callbacks will only be executed if no previous Promise has been rejected (that is, there haven’t been any errors yet). Link

They thought that a .then after the .catch would not be reached because These later callbacks will only be executed if no previous Promise has been rejected. It's not clear if this subsequent .then will be reached if an error occurs somewhere in the chain. Providing an example that illustrates the concepts of problem set 6 (toggleSpinner), would clarify it. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0