Drop-ins Initialization #31
Conversation
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
|
|
scripts/dropins.js
Outdated
|
|
||
| export default async function initializeDropins() { | ||
| // Set Commerce Mesh endpoint | ||
| mesh.setEndpoint(await getConfigValue('commerce-core-endpoint')); |
There was a problem hiding this comment.
Calling the import mesh can be confusing - as it's unrelated to actual API Mesh.
scripts/dropins.js
Outdated
| initializers.register(product.initialize, {}); | ||
| initializers.register(cart.initialize, {}); | ||
| initializers.register(checkout.initialize, {}); | ||
| initializers.register(orderConfirmation.initialize, {}); |
There was a problem hiding this comment.
Is this going to initialize all DropIns on all routes? I wouldn't expect PDP to be initialized on checkout, for example.
There was a problem hiding this comment.
@sirugh I've been bouncing back and forth with that. You are right, Maybe This is where you can initialize a global drop-in like Auth and Cart but the rest is initialized in their block.
| }); | ||
|
|
||
| checkoutRenderer.render(Checkout, { | ||
| return provider.render(Checkout, { |
There was a problem hiding this comment.
Is this meant to be standard practice for all drop-in rendering?
There was a problem hiding this comment.
Yes, if it has getInitialData it will wait for it to be resolved before rendering the page. If not, it will just render :)
Description
Initializes DropIns
Pending
Test URLs