This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Run Vsbridge Dataprovider before Custom Dataproviders #317
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.
#316 Run Vsbridge Dataprovider before Custom Dataproviders
module-vsbridge-indexer-core/Indexer/GenericIndexerHandler.php line 165
without sorting, the custom data providers are called before the core data providers (f.e. if the vendor name starts with A or B)
but only with the core data providers the necessary attribute values are added
only if we have the attribute values, we can implement logic based on Attribute Indexes
there is no option to sort data providers by xml