@divkitframework/divkit 24.2.0 → 24.4.0-patched-6cf96a434f902166380b2bb2c1e4eb41acabf148

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -272,6 +272,19 @@ Default value is `['http', 'https', 'tel', 'mailto', 'intent']`
272
272
 
273
273
  Components with an action containing a protocol from the list will be rendered as `<a>`, and clicking on them will be processed by the browser. Protocols outside the list will cause the element to be rendered as a button-like, and clicking on them causes an 'onCustomAction'.
274
274
 
275
+ ### extensions
276
+
277
+ `Map<string, DivExtensionClass>`, optional.
278
+
279
+ Allows to modify components behaviour by a custom code. DivKit contains several built-in extensions, that can be enabled with this property.
280
+
281
+ Extensions are client-side only. One can render some json on a server, than hydrate it on a client with extensions, but if these extensions modify components look, users may notice this change on a page load.
282
+
283
+ Also be aware of new releases (even minor and patch versions). Built-in extensions will remain compatible with the new code, but a custom ones can broke with it. Simple extenions, like setting attributes on a component DOM-node less likely broke, but a heavier ones, that depends on a DOM tree, tag names, events or something are on your own risk.
284
+
285
+ [Enabling built-in extensions](../divkit-examples/extensions-builtin/)
286
+
287
+ [Building of a new extension](../divkit-examples/extensions-handmade/)
275
288
 
276
289
  #### theme (EXPERIMENTAL)
277
290