I see too many people (and I’m as guilty as y’all) of using the new Components feature, to store “all the logic”. In these few days of playing with them, I learnt, that you actually need to think of the components as tools, that yes, store the logic, but shouldn’t (at least for now) be storing any …

So far the way I am approaching is based on: variable created inside component = “component variable” variable created outside component = “app variable” Logic at app level can ONLY use app variables Logic inside component can use ANY variable - app variables and/or component variables So, the …

I just redid all of my input fields as components only to realize after that I cannot reference any of the inputted text outside of the components :(( am I missing something?

Indeed, you need to emit the events with the data - on change, using triggers. Basically you’re “extending” the reach of the fields inside the component.

Oh shoot, thank you guys for the info, I got everything to work! Now let’s say I’m building a password form, and I have a button outside of my 3 components. Current Password, New Pass, and Confirm Pass. And the outside button is called Cancel. I want that button to clear the values from all three i…

I would suggest handling all the data that is not exclusive outside the component. Always think of it, in some way like this: Do my data affect only the behavior/internal logic of the component? → Component variable Does my data affect/get used outside of the scope of the component? → Outside (cl…

The reason I want to use components is because it’s so much easier to update everything at once in a unified way. All my inputs are customized and it makes them so much easier to manage as components. I will likely have over a hundred inputs, and I don’t see another alternative that’s as flexible. …

I still think you should use components (I’m not saying don’t use components - just handle the general logic outside of them) only to modify the outer state (a classic variable) as at the end of the day, you’ll be triggering the change password workflow from the outside (a workflow I’m guessing) not…

In January, based on what was said in today’s Office Hours @flo , it will be possible to expose the variable of a component, facilitating this process and not necessarily needing to use emit trigger events

You actually can do this right away if you use a different approach and are ok with modifying variables with js. Instead of creating an internal variable and expose it to the parent pass a global variable of type object as a property to the component and with js change the properties of this object.…

[Components] Some advice on Components

Ask us anything

dorilama (Mariano) December 12, 2023, 9:13pm 4

you need to use triggers, see this example.

Topic		Replies	Views
Help with Component Variables How do I?	5	857	December 9, 2023
Ways of component interaction? Ask us anything components	8	561	January 25, 2024
How can I get the variable values from a component? How do I? binding	2	473	August 23, 2024
New components versus variables How do I?	9	451	December 8, 2023
Can I change component properties within workflows? How do I?	5	326	April 12, 2024

[Components] Some advice on Components

Related topics