Revisit table and list models
The current solution, where tables and lists are based on custom item types for each COB, should be revisited. It works, but has some overhead and additional complexity that can be potentially removed.
An alternative implementation would solely rely on tuirealm’s properties and states. Things to prototype:
- COB’s need to be converted to
AttrValue::Payload(PropPayload::Map(...)), such that they can be set as the table’s or list’s content - COB’s need to be constructed from
State::Map(...), such that the application logic can process selected items
If the alternative solution turns to not reduce complexity, there’s a some middle-ground that can at least simplify the application logic:
- Add
impl From<State> for IssueItemandimpl From<State> for PatchItemetc. - possibly more.