You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current version (2.x), the StreamQuery#get is implemented to return a Promise<Stream>. This is a little awkward, and an anti pattern as it mixes two way for coding asynchronously
The proposal is to have the promise handled in the library so that stream query returns only a quad stream, unwrapped from the promise.
The text was updated successfully, but these errors were encountered:
@cristianvasquez I think this is only relevant for non-2xx status codes, or do you see other use cases? The status code could be attached to the error object like it's done by the http-errors package. Then it's possible to handle all errors with the error event of the stream. HTTP errors will have the status property.
In the current version (2.x), the
StreamQuery#get
is implemented to return aPromise<Stream>
. This is a little awkward, and an anti pattern as it mixes two way for coding asynchronouslyThe proposal is to have the promise handled in the library so that stream query returns only a quad stream, unwrapped from the promise.
The text was updated successfully, but these errors were encountered: