Automatically parse any THREE Enum property types

[jo-chemla]

It would be great if all THREE Enums property types - properties other than bool, number, string, color, vector3, transforms, array etc - could be handled all automatically without the need to do the associations on a per property basis within the triplex codebase.

For example, atm, side property and multiple other dropdowns offer no options at the moment. When set through code via the editor, a warning is shown within triplex UI, prop is controlled by code, and the value is not applied.
Probably linked to literal-union-input.tsx and prop-input.tsx, as well as useLazySubscription from @triplex/ws-client

Temporary quickfix: allow for free-form string text fields for properties which were not parsed, and when the user enters a string starting with THREE., then evaluate that code block.

[itsdouges]

@jo-chemla can you confirm what you see in the latest Triplex + Three.js release? Looks like side is now a numeric literal. Is that the same for other THREE enums?

Obviously it's not helpful seeing numbers in the UI so we'd need to improve that.

[itsdouges]

Looks like the @type/three definition has moved from enums to literals? Unless they were always like this? 🤔

[itsdouges]

This is what it will look like in the next release of Triplex:

In Editor:

In Code:

Currently don't pull out the objects into code and instead just use the literals because that is more things to handle (add/remove etc). Can update in the future if needed.

[jo-chemla]

Impressive, thanks for the updated fix this looks great!