try-triplex
Tuple inputs should set default values for missing simple types that are required when changing any value of the tuple
Right now you need to enter all values to have it flushed to the scene. Ideally we can do better than this.
In the least it would be nice if all tuple values were 0 by default so entering partial values works as expected.
It's difficult to know what a valid value is. For now the inputs will show invalid state when filling them in so you at least have a visual cue that more input is needed.
This will be released in the next version of Triplex for VS Code. It hasn't been implemented yet in Triplex Standalone.
What is the difficulty? Is something too naive about setting all number values to 0?
It's not difficult it's setting expectations correctly. Setting to 0 works for this pro, it won't work for others (like scale).
We could introduce special behaviour for some props but I'd be cautious of introducing conflicting UX.
That's a good point. I think 0 is more correct than not and we can add exceptions for cases where it isn't. But even if it is not correct, having a user replace it with a real value is as much work as we have to do now but it saves time in all the cases where you don't have to.
I'll release the current validation change and will put default values behind a feature gate to test.
It works!
Should have done this ages ago! https://x.com/dougesdev/status/1952887481373978744