You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/pages/app-development/extension-compatibility.md
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Verify that your Commerce APIs are compatible with both environments by checking
37
37
-​<Editionname="paas" /> [PaaS REST API specification](https://developer.adobe.com/commerce/webapi/rest/quick-reference/).
38
38
-​<Editionname="saas" /> [SaaS REST API specification](https://developer.adobe.com/commerce/services/reference/cloud/rest/).
39
39
40
-
​<Editionname="paas" /> **Adapt REST endpoint for older starter kit versions**
40
+
**Adapt REST endpoint for older starter kit versions**
41
41
42
42
For older versions of the starter kit, check if your code is adapted as follows:
43
43
@@ -56,7 +56,7 @@ For older versions of the starter kit, check if your code is adapted as follows:
56
56
57
57
## Commerce eventing
58
58
59
-
- ​<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
+
- ​<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.
60
60
- ​<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).
61
61
62
62
## Admin UI SDK
@@ -71,16 +71,16 @@ For older versions of the starter kit, check if your code is adapted as follows:
71
71
72
72
```javascript
73
73
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);
77
77
} 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
0 commit comments