Best Approach for Creating an Effect Wrapper for GitHub Actions Libraries
Hello guys!
If I want to make an effect wrapper for a public library, what is the best approach to the API surface I'm providing?
Make a single service and implement it or something else?
I'd like users to be able to easily mock everything they want in their tests
Libraries I'm going to wrap are ones for Github Actions:
If I want to make an effect wrapper for a public library, what is the best approach to the API surface I'm providing?
Make a single service and implement it or something else?
I'd like users to be able to easily mock everything they want in their tests
Libraries I'm going to wrap are ones for Github Actions:
@actions/*@actions/core@actions/io
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
