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

Provider default checks as parent-based #256

Open
guybedford opened this issue Mar 7, 2023 · 1 comment
Open

Provider default checks as parent-based #256

guybedford opened this issue Mar 7, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@guybedford
Copy link
Member

Currently short of the providers configuration, providers always pick up from the defaultProvider. In more complex multi-provider scenarios, we should instead always pick up the provider context from the parent unless otherwise indicated through the providers config.

@Bubblyworld Bubblyworld added the enhancement New feature or request label Mar 8, 2023
@Bubblyworld
Copy link
Contributor

So in order of precedence, provider picking should follow:

  1. there's a providers override for the parent context
  2. the parent context belongs to a particular provider
  3. the input map is mostly populated with a particular provider
  4. the defaultProvider

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants