future-plans: field detail display should use a table
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -53,6 +53,11 @@ function and own their local state.
|
|||||||
|
|
||||||
### Improvements
|
### Improvements
|
||||||
|
|
||||||
|
#### Field display in component detail should use a table
|
||||||
|
Currently rendered as CSS grid rows but columns don't align because each row is
|
||||||
|
independent. Use an actual `<table>` so name and value columns line up across all
|
||||||
|
fields. This is tabular data and a table is the right element.
|
||||||
|
|
||||||
#### Field value parser chain
|
#### Field value parser chain
|
||||||
Similar to how name formatters use a template chain, field values could be passed
|
Similar to how name formatters use a template chain, field values could be passed
|
||||||
through a parser chain that returns structured data based on field name/type hints.
|
through a parser chain that returns structured data based on field name/type hints.
|
||||||
|
|||||||
Reference in New Issue
Block a user