An enum lets you choose one value from a predefined set of options. Use enums when a property should only ever be one of a few known values—like modes, states, or variants—instead of allowing any arbitrary value like a string. For example, instead of using a string like “left”, “center”, or “right”, an enum guarantees the value is always one of those valid options.Documentation Index
Fetch the complete documentation index at: https://uat.rive.app/docs/llms.txt
Use this file to discover all available pages before exploring further.

- System enums — built-in sets of options used by the editor (for example, Horizontal Align)
- Custom enums — your own defined sets of options for your specific use case
Why not use strings or numbers?Imagine a calendar app that shows different backgrounds based on the day of the week.You could use a string like “Monday”, but it breaks if someone sets it to “Mon”.You could use a number, but it’s unclear whether the week starts on Sunday or Monday—or whether the index starts at 0 or 1.With an enum, the value must be one of the defined options, so it’s always valid and unambiguous.
Adding an enum property

Binding enums

Custom enums

Controlling Solos with enums
Use an enum to control which Solo is active by mapping each enum value to a Solo.
Create a matching enum
Create a custom enum with values that match the names and order of your Solos.