dnm: partner day #20
dnm: partner day #20
Conversation
…r third-party query in mesh Signed-off-by: Stephen Rugh <rugh@adobe.com>
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
|
|
| }, | ||
| { | ||
| "key": "commerce-core-endpoint", | ||
| "value": "https://edge-graph.adobe.io/api/1ed11f0b-4dc6-4029-8e4d-631fafb4dec4/graphql" |
There was a problem hiding this comment.
This file is just a way to force the override of adobe-demo-store site to use this commerce endpoint. In partner day, each person will have their own site + config, pointing to their own mesh already.
Signed-off-by: Stephen Rugh <rugh@adobe.com>
Signed-off-by: Stephen Rugh <rugh@adobe.com>
…onments Created 'override-configs-dev.json' and 'override-configs.json' to manage environment-specific configurations. Updated 'configs.js' to reference the new override configuration files based on the environment.
…ronment configuration. Updated 'configs.js' to reference the new configuration file.
| const fileName = 'configs-override.json'; | ||
| // if (env !== 'prod') { | ||
| // fileName = `override-configs-${env}.json`; | ||
| // } |
There was a problem hiding this comment.
@sirugh FYI — if the extension is .json, the Content Bus will be checked first. For some reason, JSON files in the repo were being prioritized only when using localhost:3000. This update ensures that all environments in this branch are forced to use the JSON override, allowing all .page and .live URLs to be previewed during the lab.
2 participants
Demonstrates GQL extensibility method of augmenting fragment for the initial query made by drop-in.
To try it out, check the repo/branch out locally,
npm iandnpm run start. Then open:http://localhost:3000/products/for-creators-by-creators-hoodie/ADB387 and see if ratings are rendered.
configs-dev.jsonis necessary only because I wanted to force a specific endpoint instead of modifying theeds configfor adobe-demo-store repo.scripts/__dropins__can be ignored - it is output ofnpm i.So only 3 files necessary:
build.mjs- tells the dropin to use new schema props on a fragmentinitializers/pdp.js- tells the pdp to allow the new prop through with the transformed datablocks/product-details/product-details.js- the pdp block that uses the new data when rendering the view--- Below is just EDS things, you can ignore. ---
Test URLs: