Wappler Version : 6.7.2
Operating System :
Server Model:
Database Type:
Hosting Type:
Expected behavior
The dmx-on:add should not trigger when the component is initialized
Actual behavior
If the tagify component has a dynamic value, the add event fires for each item contained within the value.
How to reproduce
In this example, recipe returns the dynamic value of the tagify component, and tags returns the dataset.
<meta name="ac:route" content="/test">
<dmx-serverconnect id="recipe" url="/api/1/4/recipes/recipe" dmx-param:recipe_id="10854"></dmx-serverconnect>
<dmx-serverconnect id="tags" url="/api/1/4/tags/tags"></dmx-serverconnect>
<input is="dmx-tagify" id="tagify1" name="tagify1" dmx-bind:data="tags.data.recipe_tags" tag-text="tag_text" tag-value="tag_text" dmx-on:add="run({alert:{message:'Tagify add event'}})" dmx-bind:value="recipe.data.basics.tags.groupBy(`tag_text`).keys()" min-chars="0">
Could you check if this version solves the problem:
It doesn't trigger when the component is initialized, the add event is triggered because the data is inserted after the serverconnect has finished loading it and not directly on init.
@George No change with the app connect test.
@patrick So this is the expected behavior? If so, maybe we can have a new method that is only triggered when a user adds a new item (like we have change vs update events on inputs.)
I will check, but I believe it was not possible with the tagify library to detect the difference between a user added tag or if it was added by javascript.
I'm experiencing a similar issue with the dmx-on:add tagify event when the tagify component has a dynamic value.
I have seen additional records being inserted in the DB tables without any user input.
The changed event is only triggered on user interaction, but it triggers on both adding and deleting tags.