The goal is to add support for content components (non-reusable content).
From the SDKs point of view, the components behave the same as regular content items. However, they are supported only in the rich-text elements.
The only difference is that the value of the data-type attribute is not item but component. (There is no new endpoint for Content components in the Delivery API). The components are being sent as a part of the modular content (linked items) dictionary in the same format as the regular modular content.
petrsvihlik
commented
6 years ago
Motivation
The goal is to add support for content components (non-reusable content). From the SDKs point of view, the components behave the same as regular content items. However, they are supported only in the rich-text elements.
<object type="application/kenticocloud" data-type="component" data-codename="n55afed3a_b4a3_018a_8744_3b06301b1f88"></object>The only difference is that the value of the
data-typeattribute is notitembutcomponent. (There is no new endpoint for Content components in the Delivery API). The components are being sent as a part of the modular content (linked items) dictionary in the same format as the regular modular content.Sample implementation: https://github.com/Kentico/delivery-sdk-net/pull/131/files
Checklist
How to test
Make sure rich-text elements containing components get resolved in the same manner as standard content items. Testing KC project: https://qa-deliver.global.ssl.fastly.net/ab44e0cc-9302-00c3-14ce-1362a118ad2f/items
Internal reference: DC-544