Skip to content

Commit a9dc95a

Browse files
jhadobekuflower
andauthored
Apply suggestions from code review
Co-authored-by: Sangmi <sangmil@adobe.com>
1 parent 1de146a commit a9dc95a

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

src/pages/app-development/extension-compatibility.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Verify that your Commerce APIs are compatible with both environments by checking
3737
- &#8203;<Edition name="paas" /> [PaaS REST API specification](https://developer.adobe.com/commerce/webapi/rest/quick-reference/).
3838
- &#8203;<Edition name="saas" /> [SaaS REST API specification](https://developer.adobe.com/commerce/services/reference/cloud/rest/).
3939

40-
&#8203;<Edition name="paas" /> **Adapt REST endpoint for older starter kit versions**
40+
**Adapt REST endpoint for older starter kit versions**
4141

4242
For older versions of the starter kit, check if your code is adapted as follows:
4343

@@ -56,7 +56,7 @@ For older versions of the starter kit, check if your code is adapted as follows:
5656
5757
## Commerce eventing
5858
59-
- &#8203;<Edition name="paas" /> You can register events through [XML files](../events/module-development.md#register-events) or REST endpoints. However, for plugin-type events, you may need to redeploy to generate plugins.
59+
- &#8203;<Edition name="paas" /> You can register events through [XML files](../events/module-development.md#register-events) or [REST endpoints](../events/api.md). However, for plugin-type events, you may need to redeploy to generate plugins.
6060
- &#8203;<Edition name="saas" /> SaaS supports a predefined list of events. You can manage events through the [Admin interface](../events/create-events.md) or [REST endpoints](../events/api.md).
6161
6262
## Admin UI SDK
@@ -71,16 +71,16 @@ For older versions of the starter kit, check if your code is adapted as follows:
7171
7272
```javascript
7373
if (props.ims?.token) {
74-
// When running inside Experience Cloud Shell, IMS token and orgId can be accessed via props.ims.
75-
setImsToken(props.ims.token);
76-
setImsOrgId(props.ims.org);
74+
// When running inside Experience Cloud Shell, IMS token and orgId can be accessed via props.ims.
75+
setImsToken(props.ims.token);
76+
setImsOrgId(props.ims.org);
7777
} else {
78-
// Commerce PaaS & SaaS retrieves IMS token via sharedContext from Admin UI SDK v3.0+
79-
// See https://developer.adobe.com/commerce/extensibility/admin-ui-sdk/extension-points/#shared-contexts
80-
const guestConnection = await attach({ id: extensionId });
81-
const context = guestConnection?.sharedContext;
82-
setImsToken(context?.get('imsToken'));
83-
setImsOrgId(context?.get('imsOrgId'));
78+
// Commerce PaaS & SaaS retrieves IMS token via sharedContext from Admin UI SDK v3.0+
79+
// See https://developer.adobe.com/commerce/extensibility/admin-ui-sdk/extension-points/#shared-contexts
80+
const guestConnection = await attach({ id: extensionId });
81+
const context = guestConnection?.sharedContext;
82+
setImsToken(context?.get('imsToken'));
83+
setImsOrgId(context?.get('imsOrgId'));
8484
}
8585
```
8686

0 commit comments

Comments
 (0)