Mark Lundin

All expressions for a script would be evaluated in order when any one of it's attributes is changed in the editor. So if a user toggles a check box, just...

The class is never actually initialized in the context of the editor. it would add a lot more complexity, and I'm not sure what the win would be

> I would definitely avoid using eval as much as possible. Yep [eval() is evil](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval#never_use_direct_eval!) > For the conditions, common use case is not just true/false (checkbox-dependant), but equal to...

This could be an easy lift where we use similar UX to existing collapsible content. Simply show a toggle on the folder when the interface has an `enabled` property, and...

So I have an initial implementation of this. There are 2 attribute conditions `@enabledWhen` and `@visibleWhen` which will enabled/hide the attribute in the UI depending upon the expression and state....

Ha! Yes literally just discussed this. We'll stick to JS operators

Not sure I 100% follow, but it would support attributes that depend on combobox attributes ```javascript /** @enum {number} */ const LightsEnum = { OFF: 0, ON: 1, UNKNOWN: 3...

> You still need to cull `.env`, `.gitignore`, `eslint.config.mjs` plus whatever else might not be needed. removed `.gitignore`, `eslint.config.mjs`. `.env` is used to store the config settings

Where do we want this export option @willeastcott @slimbuck. As an option in the dropdown? Let me know, so I can update and we can get this merged.

Is it possible to use the layout: "raw" with V4?