-
Notifications
You must be signed in to change notification settings - Fork 24
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
Expose resolveProxyProvider function as we expose resolveProxyProviders #130
Comments
I had that idea in my mind for a while, too. Do you mean resolving proxy providers individually? I think it could work if we added an array of proxy provider injection tokens as an array to the |
Exactly! That would work perfectly.
|
I think another good improvement together with this would be an |
I'm not a fan of adding features unless they solve a concrete problem. Let's start with selective resolution of proxy providers only. |
I see, same, just thought as it'll be useful to follow DRY while I add cronjobs that will run for every tenant db but no worries about that for now. Btw I appreciate the enhancement of resolving proxy providers individually |
Released in |
Awesome, thanks for the update! |
Is it possible to expose
resolveProxyProvider
as we exposeresolveProxyProviders
? It gives us the flexibility of resolving the providers properly when needed.The text was updated successfully, but these errors were encountered: