Passing Values vs. References in Dropzone Variables - Update variable wrapped in object

[rikoentw]

I’d also like to avoid global variables. That’s why I am trying to get reactivity by using dropzone data.

@Broberto

Always try to use props. Passing objects lets you update them…

In my experience, properties seem to be read only, even when passing objects. I need to use component variables initialized with the property value and then work with the variable. How do you make it work with props directly, if I understood you correctly?

Do you have experience with arrays? In my understanding arrays should be objects and therefore be passed by reference.

Reference:

How can I change a component property inside of a component?

The property is managed exclusively by the instances, so you cannot really. What you can do is: Create a variable You can manipulate and bind to this variable Make a workflow ‘On prop change’ and then update the variable when the property changes

How can I change a component property inside of a component?

Same applies as my first comment here, use a component variable to manipulate and change text and only use the prop for the initial value

Can I change component properties within workflows?

Property should not be change by the component, as they are own by the parent/exterior of the component. To implement your pattern (two ways binding) you should emit a trigger (you can call it onChange for exemple) and update your variable using a workflow on your instance. You can also expose a workflow to modify an internal variable from outside. Other option If you wish each instance to always have this value, you can define an internal variable and expose it, and have only an initial val…