sfccdevops / sfcc-devtools Goto Github PK

Support for SFRA sites using Page Designer Components.

• Currently on site, when you inspect a slot and notice it's a Page Designer component, you are required to go into business manager and search through the growing list of assets. (SFRA doesn't even have the ability to link directly to it in the Toolkit Icon)

The component generated comments have the unique data for the asset.
Typical Page designer component example:
<!-- dwMarker="rinclude" dwPipelineTitle="Internal - Page Designer" dwIsController="false" dwPageId="Component-Asset_Name" -->

Just need the extension to look for that and swap out the url with the one below:
https://${domain}/on/demandware.store/Sites-Site/default/ViewLdsBusinessManagerScreen-PageDesigner/#/edit/page/${dwPageId}

Please add an extension for the new Edge browser as well. You should be able to port the Chrome version to Edge without a single code change 99% of the time.

https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension

Overview:

Have an option to set the default linking for "Open in Business Manager".
So instead of being based off whether or not you are viewing staging or production, allow the user to set the link to always open business manager in the staging instance.

Acceptance Criteria:

This will allow the convenience of finding an asset currently in production, and opening it in the staging instance of business manager.

Steps to Duplicate ( required for bug reports ):

• Have production site open
• Open inspector and select a dwContentID comment.
• Clicking the button for "Open in Business Manager" will open the Production version of Business Manager (which is currently an intended feature of the extension).

System Info ( required for bug reports ):

MacOS 10.15.4
Chrome Version 81.0.4044.92

Overview:

When selecting the Content ID comment, the SFCC window only shows the header "Content Slot", without the button to link to business manager.

Steps to Duplicate:

Open inspector and select the dwContentID comment.

System Info:

MacOS version: 10.15.3
Chrome version: 79.0.3945.130

Overview:

When clicking on a Content Slot comment, the correct label will show, but the button is missing.
I'm wondering if it's because of the siteID missing from the comment, so the code below doesn't build the slotURL correctly.
But it should still build the button, so I'm at a loss of what it could be exactly.

if (props.type === 'slot' && props.id && domain && siteID)