Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: abstract out more "providers" #25

Open
brent-hoover opened this issue Jun 17, 2024 · 0 comments
Open

feat: abstract out more "providers" #25

brent-hoover opened this issue Jun 17, 2024 · 0 comments
Labels
tech-debt Just my catch-all term for work that makes the app better but doesn't add a user feature

Comments

@brent-hoover
Copy link
Contributor

brent-hoover commented Jun 17, 2024

Do similar to what EspressoTS is doing here: https://doc.expresso-ts.com/docs/overview/providers where we de-couple the specific implementation of things usage. I think email providers will be a good place to try this out on

You should also be able to easily create your own type of provider type, say payment or fulfillment providers through a plugin, that then other plugins could fulfill. Again similar to how RC used to have a "payment" plug, that would then have various payment provider implementations.

@brent-hoover brent-hoover added the tech-debt Just my catch-all term for work that makes the app better but doesn't add a user feature label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech-debt Just my catch-all term for work that makes the app better but doesn't add a user feature
Projects
None yet
Development

No branches or pull requests

1 participant