Skip to content

Conversation

@thiemowmde
Copy link
Contributor

To know this is critical for external callers as well as internally. Look how the newEntityDeserializer method uses the return values from newItemDeserializer and newPropertyDeserializer: in a DispatchingDeserializer, which requires the values to be of type DispatchableDeserializer. Same is true for usages outside of this component. So this information is already public, just not documented properly.

@thiemowmde thiemowmde added this to the 2.7.0 milestone Sep 19, 2017
* @return Serializer
* @return DispatchableSerializer
*/
public function newStatementSerializer() {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I touched this because the corresponding deserializer is already documented as "dispatchable".

This is for a historical reason: certain API modules have been designed in a way they can accept both statement as well as claim serializations. Therefor statement and claim serializers and deserializers must be dispatchable. And they are, it's just the documentation that is misleading. I think we should fix this, even if we are not using this as a feature at the moment.

@mariushoch
Copy link
Member

+1 sounds sensible

@mariushoch mariushoch merged commit fbd19f3 into master Mar 29, 2018
@mariushoch mariushoch deleted the publicInterfaces branch March 29, 2018 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants