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.
Problem Statement:
Many people ask how to:
Solution:
To standardize the process, we are using the new product extensions loader, which allows business users to compose loaders via the deco UI.
How does it work?
Go to Block > Loaders and filter by extensions. You will see a screen similar to this image.
Now, enter the desired extension (let's say products.ts). Next, as the original integration, add the one you originally had, for example, VTEX Legacy Search, and configure it as usual. Then, click on 'The Data Extensions' and add the desired extension, in this case, 'VTEX Integration - Extra Info.' Now, you can select "simulate," "Similars," and "Kit items" to be brought in by this composed loader.
Why Composed Loaders and not just another option in the native loader?
We are integrating with various other players in the market and have observed the need to compose loaders. Some of these players require certain features from the native VTEX loaders, and by allowing the composition of loaders through the UI, we have found that we can offer more flexibility to the store owner in composing different APIs.