This includes adjusting the QueryCondition component and should probably be done after T270256
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Charlie_WMDE | T268941 (MS 3) allow to include results from subclasses | |||
| Resolved | Lydia_Pintscher | T268814 (MS 3) allow to query for Item values | |||
| Resolved | Michael | T270257 Create a dispatcher that maps the property datatype to value input type (Lookup, TextInput) |
Event Timeline
Comment Actions
I'm thinking about this more. Maybe it would make sense to deal with this just inside a (yet to be created) ValueInput component that decides based on the datatype which Input to display? And maybe inside ValueTypeDropDown in the future as well?
But this might also make a difference for how we store the value in the store. Needs more thought 🤔