There doesn’t seem to be any documentation on the schema field when creating an Event Trigger for a component.
Does anyone care to share?
1 Like
@weweb-team ???
It is just an option to define a “schema” that will be displayed in the event result when you use that Trigger, it is a mock thing, to allow you to more easily access the keys of your event’s result. E.g in my dropdown component, I know that I will return some values inside the object, I didn’t want my users to guess, so I set up the Event schema so it’s there for them available. It is mock data, more of an utilty, it’s not required, but for good UX it’s essential.
2 Likes
I found that the Event value doesn’t overwrite the default Event Schema. It seems that we cannot pass a payload based on a variable, just don’t know exactly if it is a current limitation or a bug.
The workaround I found for this is by updating a component variable that can be accessed by outside.
Schema is just informative, the result is the real data.