Feature Request: await tap
See original GitHub issueHello everyone,
right now the “tap” documentation reads:
Perform a side-effect for each event in stream.
Since it’s a function which is primarily aimed at running side-effects, I would expect it to provide some await mechanics. Example implementation: if the provided function returns a Promise, wait until its resolved, discard its value and then go on with the stream.
Hope such feature makes sense.
Cheers
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
4483 - Feature Request: Support async/await functions - v8
Issue 4483: Feature Request: Support async/await functions ... (async function(){await 1;debugger})() causes a tab crash in Chrome.
Read more >Task asynchronous programming model - Microsoft Learn
Lists and demonstrates the benefits of using async and await to access files. Task-based asynchronous pattern (TAP), Describes an asynchronous ...
Read more >Getting Started - Node Tap
Each file should cover a feature or concept. For small Node modules, ... test/hello-world.js const tap = require('tap') tap.pass('this is fine').
Read more >How to await inside RxJS subscribe method - Stack Overflow
switchMap can cancel in-flight network requests! – Robert Rendell. Apr 23, 2021 at 10:18. Add a ...
Read more >How to use promises - Learn web development | MDN
Inside an async function, you can use the await keyword before a call to a function that returns a promise. This makes the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Now that @most/core is the recommended package, it’s even easier to create community packages, since it doesn’t rely on prototypes. There’s even https://github.com/mostjs-community 😄
Closing since this can be provided by a community package.
I’ve been poking around the most docs and now old issues to learn more about it – seems like one of the goals of most is a small API surface, so the idea of an asynchronous tap seems like it would be best placed in the community repos as suggested above.
Would you consider this issue a good candidate to close on account of lack of recent activity?