[
https://issues.apache.org/jira/browse/TINKERPOP-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487927#comment-16487927
]
ASF GitHub Bot commented on TINKERPOP-1945:
-------------------------------------------
Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/842
After thinking a bit more about this, my conclusion was that deprecating
those types doesn't really make sense unless we plan on GraphSON 4.0 as we
couldn't remove the types before that. Since we already have those types since
GraphSON 2.0 and they can only be used when the extended module is explicitly
selected I guess that we don't have to take immediate action at the moment.
Usage of the extended types is probably relatively low in general anyway.
But for the new serialization format @jorgebay suggested we should really
check which types we want to support at all. I added a comment to the ticket so
we don't forget that aspect.
So @danielcweber, looks like it would be best if you could remove all
deserializers again for which no serializer exists and vice versa. Sorry for
the unnecessary work you put into this.
> Add support for extended GraphSon types to Gremlin.net
> ------------------------------------------------------
>
> Key: TINKERPOP-1945
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1945
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Reporter: Daniel C. Weber
> Priority: Minor
>
> While Gremlin.net can properly serialize and deserialize all of the core
> GraphSon types, support for most of the extended types as described
> [here|[http://tinkerpop.apache.org/docs/3.3.2/dev/io/#_extended]] is lacking.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
