[BUG]: "component:add" event triggers when components are moved

[nojacko]

Taken from https://github.com/artf/grapesjs/wiki/API-Editor

component:add - Triggered when a new component is added to the editor, the model is passed as an argument to the callback

My understanding is that the component:add should only be called when the block is dragged in from the blocks panel and dropped into the editor. I don't think this should happen when a block is moved around the editor (that's what component:update is for...)

Reproduce

1. https://jsfiddle.net/szLp8h4n/11/
2. Move any of the text components around in the page.
3. An alert will be displayed.

---

Great project btw. 👍

[artf]

Thanks for the catch James, I'll fix it for the next release

[lv-alex]

hi,
When is the next release? Is it possible for us to fix it on our end before the release? We are seeing this issue now and our release goes out in 2 weeks.

thank you
ca

[artf]

@lv-alex I planned to release for the end of this week

[lv-alex]

thank you @artf . We will try it out

[lv-alex]

It works. Thank you @artf

[japo32]

Is this anywhere in the new documentation? I can't seem to find any reference to component:add

[artf]

@japo32 all available public events are documented here: https://grapesjs.com/docs/api/editor.html#available-events

[seifelhoseiny]

Any update on this issue? It still calls component:add event when I simply move a component around.

[lukjaki]

It also triggers component:add when selecting different components.