psychedelicious dba8c43ecb feat(ui): explicit field type cardinality
Replace the `isCollection` and `isCollectionOrScalar` flags with a single enum value `cardinality`. Valid values are `SINGLE`, `COLLECTION` and `SINGLE_OR_COLLECTION`.

Why:
- The two flags were mutually exclusive, but this wasn't enforce. You could create a field type that had both `isCollection` and `isCollectionOrScalar` set to true, whuch makes no sense.
- There was no explicit declaration for scalar/single types.
- Checking if a type had only a single flag was tedious.

Thanks to a change a couple months back in which the workflows schema was revised, field types are internal implementation details. Changes to them are non-breaking.
2024-05-20 11:28:33 +10:00
..
2024-04-19 09:32:56 -04:00
2024-01-12 08:02:59 +11:00
2023-07-28 09:46:44 -04:00
2024-05-15 14:09:44 +10:00
2024-04-15 07:54:36 +10:00
2024-05-15 14:09:44 +10:00
2024-03-13 22:43:20 +11:00
2024-03-01 10:42:33 +11:00