Browse Source

Fix typo in 'isComponent' reference

pull/6727/head
Matt Murphy 2 weeks ago
committed by GitHub
parent
commit
5d1eb803b3
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
  1. 2
      docs/modules/Blocks.md

2
docs/modules/Blocks.md

@ -139,7 +139,7 @@ Using HTML strings as `content` is not wrong, in some cases you don't need the f
In such a case, all rendered elements will be converted to the best suited default component (eg. `.el-Y` elements will be treated like `text` components). The user will be able to style and drag them with no particular restrictions.
Thanks to Components' [isComponet](Components.html#iscomponent) feature (executed post parsing), you're still able to bind your rendered elements to components and enforce an extra logic. Here an example how you would enforce all `.el-Y` elements to be placed only inside `.el-X` one, without touching any part of the original HTML used in the `content`.
Thanks to Components' [isComponent](Components.html#iscomponent) feature (executed post parsing), you're still able to bind your rendered elements to components and enforce an extra logic. Here an example how you would enforce all `.el-Y` elements to be placed only inside `.el-X` one, without touching any part of the original HTML used in the `content`.
```js
// Your component

Loading…
Cancel
Save