- Ponder the name a bit. Parser vs deserializer…
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T91505 [Epic] Adding new datatypes to Wikidata (tracking) | |||
Open | None | T214884 [ES-M2]: [EPIC] Linking EntitySchemas in statements | |||
Resolved | Ifrahkhanyaree_WMDE | T354778 Build a solution in Wikibase for EntitySchemas to be returned with valuetype wikibase-entity | |||
Resolved | Ifrahkhanyaree_WMDE | T359421 🐙 Enable data type specific parser-factory-callback | |||
Resolved | Jakob_WMDE | T360599 🐙 Add the field to DataTypeDefinitions |
Event Timeline
Comment Actions
If I'm not mistaken there is already a field in DataTypeDefinitions for exactly this purpose called parser-factory-callback. From the docs: "ValueParser for this data type" which is what we want. Looking through the code, this field so far was effectively only used for *value* type definitions. A few extensions do use it (codesearch) for data type definitions, but most (all of the ones active on wikidata) only copied the default code for the corresponding value type, which doesn't have any effect.
I believe this means that there is no code to be written for this task. For T360605 we just need to elaborate on the consequences of using it and change the docs entry from "repo only" to "client and repo".