refactor: move getPaymentMethodConfigByName to context #5684
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #5653
Impact: minor
Type: feature|refactor
Issue
getPaymentMethodConfigByNamewas used across many pluginsSolution
For the sake of keeping our plugins contained, we are adding this method,
getPaymentMethodConfigByNameto thecontextto use instead of importing from thepaymentspackage directly.Breaking changes
Any custom code which uses
getPaymentMethodConfigByNameby direct import will need to update to use thecontext.queries.getPaymentMethodConfigByNameinsteadTesting