Repository navigation
[InlineEdit]: New TEDI-Ready component #199
Description
https://github.com/TEHIK-EE/tedi-design-system/issues/193
Figma
- no API changes
- Move to TEDI-Ready
- Add unit test
- improve WCAG for toggle button
- improve props descriptions
- add documentation to ZeroHeight
| Name | Required/Optional | Description | Type | Possible Values | Default |
|---|---|---|---|---|---|
className |
Optional | Classname for the button/displayed content | string |
Any valid CSS class name | |
content |
Required | Content displayed when the field is hidden. | React.ReactNode |
Any valid React node | |
fieldType |
Required | Specifies the type of hidden field. | 'textfield' | 'select' | 'datetime' |
'textfield', 'select', 'datetime' |
|
fieldOptions |
Required | Configuration options for the specified field type. | TextFieldProps (for textfield), SelectProps (for select), DateTimePickerProps (for datetime) |
Based on the fieldType |
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
kasparsuvi1 commentedon Jan 24, 2025
This is legacy component from STAR project, i dont think it's needed to be moved to TEDI. It's not with very good UX and shouldn't be recommended from Tedi probally. Im pretty sure nobody else is using it also. (For legacy support we can keep in community?)
airikej commentedon Jan 24, 2025
If that's the case we could add legacy tag to it and keep it in Community. Only problem is currently it's designed in Figma. What is your opinion on that @karolin-kivisikk would designers miss this component if we removed it? Or are there good reasons to keep it?
karolin-kivisikk commentedon Jan 24, 2025
Actually, when I went through the components then someone at the Design meeting said that it's needed but I don't remember which project was it. It was some newer project I think who wanted to use it inside of a table.
From UX perspective yes it's not a good practice but if it's used in some inner projects only for officers then it's fine I guess, but not a preferred solution of course.
But true if the usage is so low that maybe it's best to leave it in the Community? I have to think what to do with the Figma design then, it's published some time ago already.
tobre6 commentedon Jan 24, 2025
I can see some business value, but name is misleading.
airikej commentedon Feb 26, 2025
Low priority
[-]Hidden field[/-][+][HiddenField]: New TEDI-Ready component[/+]56 remaining items
feat(inline-edit): add TEDI-Ready InlineEdit component #199
intermetric commentedon Oct 23, 2026
@karolin-kivisikk Mõlema teostuse muudatuste kokkuvõte ja Storybooki lingid on Angulari issue kommentaaris.
karolin-kivisikk commentedon Oct 27, 2026
Feedback kokku kogutud: TEDI-Design-System/angular#650 (comment)
feat(inline-edit): add TEDI-Ready InlineEdit component #199
feat(inline-edit): address design review feedback #199
intermetric commentedon Oct 30, 2026
@karolin-kivisikk Reacti pool on samuti uueks ülevaatuseks valmis. Paranduste kokkuvõte.