Refactor all components to use expandable data #10

Merged
BobdaFett merged 11 commits from feature/multi-entry-data into main 2025-09-26 16:13:29 +00:00
11 Commits
Author SHA1 Message Date
alphafetus 7786ee7ff3 chore: move value_type.rs to common module 2025-09-26 12:10:20 -04:00
alphafetus c573263f48 feat: complete refactor of all data structures and fix serialization 2025-09-26 12:09:38 -04:00
alphafetus f2d8688c0c feat: refactor checkbox on_change to use match statements for readability 2025-09-25 13:29:23 -04:00
alphafetus 059f904f5d feat: update checkbox component to use open-ended structures
Commit also includes changes to other components that make unused props optional.
2025-09-25 12:31:47 -04:00
alphafetus b460c3b3fd feat: implement correct display of values on init for text field 2025-09-25 10:52:26 -04:00
alphafetus 1adeb5e07f feat: update select component to use open-ended structures (for real this time)
A previous commit incorrectly called out the select component, except it really updated the radio component.
2025-09-25 10:38:42 -04:00
alphafetus 96ebfab414 feat: update select component to use open-ended structures 2025-09-25 10:10:19 -04:00
alphafetus 7a453ad367 feat: update text field to use open-ended structures 2025-09-25 09:29:04 -04:00
alphafetus 6512f5fe13 chore: add missing dependencies for Store macro 2025-09-19 12:31:04 -04:00
alphafetus 39996319ba feat: alter OutlinedTextField to use ValueType enum
Also implemented extra error checking when the values are passed as the incorrect type. For example, the only accepted types are strings and numbers, so that will be checked and handled accordingly.
2025-09-19 12:30:27 -04:00
alphafetus 0d4bbc9e70 chore: implement basic logic to show a text field in the MultiEntry component
This logic does not support any info types other than a String, represented by an OutlinedTextField. To support more, this will likely need to completely overhaul every input component so that they accept the ValueType as a primary argument.
2025-09-16 19:08:13 -04:00