- Notifications
You must be signed in to change notification settings - Fork93
Closed
Description
Usually, when we write async stuff in specs we do something like this:
The steps to do a foopy are given by the following algorithm. The algorithm runs asynchronously and returns a Promise:
- Let
pbe a newly-created promise.- Return
pand run the remaining steps asynchronously.- If the foopy is not bary enough, then:
- 3.1. Let
ebe a new Error...- 3.2. Reject
pwithe
- Resolve
pwith a new Baz
In the examples given in the spec writing guide, step 2 is omitted. Is this on purpose? Or is doing something like 2. wrong and specs should be written differently?
Metadata
Metadata
Assignees
Labels
No labels