Change Details

To make use of the new mechanism implemented in the patch from the Product Platform team, we need to make some changes on the EntitySchema side. When parsing statement/qualifier/reference values, Wikibase will take into account the corresponding Property's data type and not only the value type. A data type specific value parser can be registered with the data type definition (here: `EntitySchema`). This will allow serialized `EntitySchema` values to contain `type`: `wikibase-entityid` without being parsed as an `EntityIdValue`. The changes that are required are: * New value type * New parser/deserializer * Adjust validators * UI “expert” component

To make use of the new mechanism implemented in the patch from the Product Platform team, we need to make some changes on the EntitySchema side. When parsing statement/qualifier/reference values, Wikibase will take into account the corresponding Property's data type and not only the value type. A data type specific value parser can be registered with the data type definition (here: `EntitySchema`). This will allow serialized `EntitySchema` values to contain `type`: `wikibase-entityid` without being parsed as an `EntityIdValue`. The changes that are required are: * New value type * New parser/deserializer * Adjust validators **Acceptance criteria** [] Users are able to create an EntitySchema data value type statement [] Users are able to load an EntitySchema data value type statement and it is linked to the EntitySchema

To make use of the new mechanism implemented in the patch from the Product Platform team, we need to make some changes on the EntitySchema side. When parsing statement/qualifier/reference values, Wikibase will take into account the corresponding Property's data type and not only the value type. A data type specific value parser can be registered with the data type definition (here: `EntitySchema`). This will allow serialized `EntitySchema` values to contain `type`: `wikibase-entityid` without being parsed as an `EntityIdValue`. The changes that are required are: * New value type * New parser/deserializer * Adjust validators **Acceptance criteria** [] Users are able to create an EntitySchema data value type statement * UI “expert” component [] Users are able to load an EntitySchema data value type statement and it is linked to the EntitySchema