Provide a description of the task
A follow-up of #6049.
When we first created the latter there were limited use cases and it worked fine. As the new table form arrived I discovered we need to label other (non-input) components like drop–downs as well.
I created the LabeledView with some helpers to cover all possible cases (and used in in table (cell) props forms) but I'm not 100% sure about it's interface. Also if we decide to deprecate LabeledInputView there will be lots of (simple) changes across the repos (image, link, media).
Things to decide:
- Is the component OK? (API/interface)
- Do we need anything more?
- Should we deprecate
LabeledInputView now?
- For how long should it exist in our codebase before we remove it?
Provide a description of the task
A follow-up of #6049.
When we first created the latter there were limited use cases and it worked fine. As the new table form arrived I discovered we need to label other (non-input) components like drop–downs as well.
I created the
LabeledViewwith some helpers to cover all possible cases (and used in in table (cell) props forms) but I'm not 100% sure about it's interface. Also if we decide to deprecateLabeledInputViewthere will be lots of (simple) changes across the repos (image, link, media).Things to decide:
LabeledInputViewnow?