Reason for tapError 2nd arg being a function that must return an Effect
Hi, nooby question I guess ..
Why tapError 2nd arg is a function that must return an Effect ? Is there a noop Effect or good practice if I just want to do something like:
Why tapError 2nd arg is a function that must return an Effect ? Is there a noop Effect or good practice if I just want to do something like:
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
