Scenario to look into:
- create property with a datatype that defines parser-factory-callback
- immediately use the new property in a statement
- see if anything goes wrong somewhere
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 | T362844 Investigate behavior of newly created properties with data type specific value parser |
Event Timeline
Comment Actions
I tested this with a simple e2e test that does the following: 1. create item, 2. create property with data type item, 3. create statement on item using the newly created property, 4. get the new statement. This all worked fine out of the box, so I added an artificial delay to the DataUpdater that inserts the property info which is needed for the data type lookup. Interestingly the statement creation never failed, because it uses the data type lookup that has a fallback on top of the property info based lookup. In step 4 the statement value shows the UnDeserializableValue serialization while the data type lookup fails.