It would be great to know the execution context for actions that are executed as a result of a trigger/event callback. There are a couple of things like this that are missing that would help make working in UI Bakery more functional and data driven.
Other examples of this type of functionality:
-
To be able to identify the uib component name for custom components when operating in the context of the custom component code itself, since the exposed surface for ui components on the uib editor side is via their name (in ui..) Hopefully that makes sense. I currently have to do some hacky feeling things to get similar functionality when these props could just be passed along instead.
-
A way to reference the current component when setting properties inside itself in the uib editor. For example, lets say you’re setting up a trigger on click and want to pass params to the action, being able to do something like this.name instead of ui.componentNameWeWant.name would be great.
-
A way to programmatically interact with and configure uib component data. It would be great to be able to create tooling inside the uib editor for interacting with uib components themselves. For example, to wire trigger events from buttons to specific actions automatically according to whatever logic I want to use. I can conceive of ways to accomplish parts of this with what we have now, but it always feels brittle and error prone to depend on work arounds for fundamental parts of the dev workflow.
Thank you for your consideration!