psychedelicious
90c4c10e14
feat(ui): show batch group in node title
2025-01-17 12:34:54 +11:00
psychedelicious
30e33d30d5
fix(ui): handle batch group ids of "None" correctly
2025-01-17 12:34:54 +11:00
psychedelicious
3df3be6c34
tweak(ui): enum field selects have size="sm"
2025-01-17 12:34:54 +11:00
psychedelicious
4e917bf2b2
chore(ui): typegen
2025-01-17 12:34:54 +11:00
psychedelicious
26e6e28a13
feat(nodes): add title for batch_group_id field
2025-01-17 12:34:54 +11:00
psychedelicious
f9cee42a06
tweak(ui): node editor layout padding
2025-01-17 12:34:54 +11:00
psychedelicious
1b8da023b8
chore(ui): typegen
2025-01-17 12:34:54 +11:00
psychedelicious
05f1026812
feat(nodes): batch_group_id is a literal of options
2025-01-17 12:34:54 +11:00
psychedelicious
ca1bd254ea
feat(ui): rename "link_id" -> "batch_group_id"
2025-01-17 12:34:54 +11:00
psychedelicious
29645326b9
chore(ui): typegen
2025-01-17 12:34:54 +11:00
psychedelicious
c23a2abc82
feat(nodes): rename "link_id" -> "batch_group_id"
2025-01-17 12:34:54 +11:00
psychedelicious
803ec8e904
feat(ui): add zipped batch collection size validation
2025-01-17 12:34:54 +11:00
psychedelicious
0abc0be931
fix(ui): allow batch nodes without link id (i.e. product batch nodes) to have mismatched collection sizes
2025-01-17 12:34:54 +11:00
psychedelicious
edff16124f
feat(ui): support zipped batch nodes
2025-01-17 12:34:54 +11:00
psychedelicious
2e4110a29a
chore(ui): typegen
2025-01-17 12:34:54 +11:00
psychedelicious
7ee51f3e14
feat(nodes): add link_id field to batch nodes
...
This is used to link batch nodes into zipped batch data collections.
2025-01-17 12:34:54 +11:00
psychedelicious
8ae75dbc35
chore(ui): typegen
2025-01-17 12:34:54 +11:00
psychedelicious
9265716b07
chore(ui): lint
2025-01-17 12:19:04 +11:00
psychedelicious
27b9c07711
chore(ui): typegen
2025-01-17 12:19:04 +11:00
psychedelicious
9dcbe3cc8f
tweak(ui): number collection styling
2025-01-17 12:19:04 +11:00
psychedelicious
30165f66c3
feat(ui): string collection batch items are input not textarea
2025-01-17 12:19:04 +11:00
psychedelicious
deb70edc75
fix(ui): translation key
2025-01-17 12:19:04 +11:00
psychedelicious
d82d990b23
feat(ui): add number range generators
2025-01-17 12:19:04 +11:00
psychedelicious
2c64b60d32
Revert "feat(ui): rough out number generators for number collection fields"
...
This reverts commit 41cc6f1f96bca2a51727f21bd727ca48eab669bc.
2025-01-17 12:19:04 +11:00
psychedelicious
4e8c6d931d
Revert "feat(ui): number collection generator supports floats"
...
This reverts commit 9da3339b513de9575ffbf6ce880b3097217b199d.
2025-01-17 12:19:04 +11:00
psychedelicious
9049e6e0f3
Revert "feat(ui): more batch generator stuff"
...
This reverts commit 111a29c7b4fc6b5062a0a37ce704a6508ff58dd8.
2025-01-17 12:19:04 +11:00
psychedelicious
3cb5f8536b
feat(ui): more batch generator stuff
2025-01-17 12:19:04 +11:00
psychedelicious
38e50cc7aa
tidy(ui): abstract out batch detection logic
2025-01-17 12:19:04 +11:00
psychedelicious
5bff6123b9
feat(nodes): add default value for batch nodes
2025-01-17 12:19:04 +11:00
psychedelicious
d63ff560d6
feat(ui): number collection generator supports floats
2025-01-17 12:19:04 +11:00
psychedelicious
acceac8304
fix(ui): do not set number collection field to undefined when removing last item
2025-01-17 12:19:04 +11:00
psychedelicious
96671d12bd
fix(ui): filter out batch nodes when checking readiness on workflows tab
2025-01-17 12:19:04 +11:00
psychedelicious
584601d03f
perf(ui): memoize selector in workflows
2025-01-17 12:19:04 +11:00
psychedelicious
b1c4ec0888
feat(ui): rough out number generators for number collection fields
2025-01-17 12:19:04 +11:00
psychedelicious
db5f016826
fix(nodes): allow batch datum items to mix ints and floats
...
Unfortunately we cannot do strict floats or ints.
The batch data models don't specify the value types, it instead relies on pydantic parsing. JSON doesn't differentiate between float and int, so a float `1.0` gets parsed as `1` in python.
As a result, we _must_ accept mixed floats and ints for BatchDatum.items.
Tests and validation updated to handle this.
Maybe we should update the BatchDatum model to have a `type` field? Then we could parse as float or int, depending on the inputs...
2025-01-17 12:19:04 +11:00
psychedelicious
c1fd28472d
fix(ui): float batch data creation
2025-01-17 12:19:04 +11:00
psychedelicious
0c5958675a
chore(ui): lint
2025-01-17 12:19:04 +11:00
psychedelicious
912e07f2c8
tidy(ui): use zod typeguard builder util for fields
2025-01-17 12:19:04 +11:00
psychedelicious
f853b24868
chore(ui): typegen
2025-01-17 12:19:04 +11:00
psychedelicious
4f900b22dc
feat(ui): validate number item multipleOf
2025-01-17 12:19:04 +11:00
psychedelicious
5823532941
feat(ui): validate string item lengths
2025-01-17 12:19:04 +11:00
psychedelicious
bfe6d98cba
feat(ui): support float batches
2025-01-17 12:19:04 +11:00
psychedelicious
c26b3cd54f
refactor(ui): abstract out helper to add batch data
2025-01-17 12:19:04 +11:00
psychedelicious
c012d832d2
fix(ui): typo
2025-01-17 12:19:04 +11:00
psychedelicious
9d11d2aabd
refactor(ui): abstract out field validators
2025-01-17 12:19:04 +11:00
psychedelicious
a5f1587ce7
feat(ui): add template validation for integer collection items
2025-01-17 12:19:04 +11:00
psychedelicious
0b26bb1ca3
feat(ui): add template validation for string collection items
2025-01-17 12:19:04 +11:00
psychedelicious
0f1e632117
feat(nodes): add float batch node
2025-01-17 12:19:04 +11:00
psychedelicious
b212332b3e
feat(ui): support integer batches
2025-01-17 12:19:04 +11:00
psychedelicious
90a91ff438
feat(nodes): add integer batch node
2025-01-17 12:19:04 +11:00
