This tracks the implementation of the outcome of T112544: [RFC] Decide on mechanism to dispatch formatting per property id.
Context: The use case currently is the formatterUrl property info. We cannot get the formatter url within the value formatters because it depends on the property id. Therefore, the decision which formatter/which formatting options to use must be made on the snak level, in particular PropertyValueSnakFormatter.
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Bene | T95684 [Story] Format identifiers as Links | ||
| Resolved | Tobi_WMDE_SW | T112753 Create a mechanism for datatype specific Snak rendering (to allow formatting based on per-property information) | ||
| Resolved | daniel | T112754 [Task] Use DataTypeDefinitions in OutputFormatSnakFormatterFactory | ||
| Resolved | hoo | T112756 [Task] Add property ID parameter to the wbformatvalue API | ||
| Resolved | Bene | T112544 [RFC] Decide on mechanism to dispatch formatting per property id | ||
| · · · |
@Tobi_WMDE_SW: turns out I already did that, see T112755: [Task] Add support for SnakFormatter factory callbacks to DataTypeDefinitions and blockers.
I'll move this to "done" in the sprint, since the breakdown is done, but keep it open, since the blockers are not implemented.