cedar-embeddable-editor 1.0.16 → 1.1.0
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 +21 -0
- package/cedar-embeddable-editor.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -282,7 +282,28 @@ If that file is also missing, the built-in `de` map would be the next. As this d
|
|
|
282
282
|
|
|
283
283
|
Information about the loading process is logged onto the console with the `CEE TRACE` prefix.
|
|
284
284
|
|
|
285
|
+
### Listening for changes
|
|
285
286
|
|
|
287
|
+
If you need to listen to data changes inside the embeddable editor, you can use the existing `change` DOM events. We added custom events in case of a multi-instance add, copy and delete operations, so you can listen to all the events on the instance.
|
|
288
|
+
|
|
289
|
+
An example in Angular is:
|
|
290
|
+
|
|
291
|
+
- `component.html`:
|
|
292
|
+
```html
|
|
293
|
+
<cedar-embeddable-editor
|
|
294
|
+
[config]="conf"
|
|
295
|
+
[templateObject]="template"
|
|
296
|
+
[instanceObject]="instance"
|
|
297
|
+
(change)="logChange($event)"
|
|
298
|
+
></cedar-embeddable-editor>
|
|
299
|
+
```
|
|
300
|
+
|
|
301
|
+
- `component.ts`:
|
|
302
|
+
```typescript
|
|
303
|
+
logChange(event) {
|
|
304
|
+
console.log('CHANGE', event);
|
|
305
|
+
}
|
|
306
|
+
```
|
|
286
307
|
|
|
287
308
|
## Example Applications
|
|
288
309
|
|