Github user PommeVerte commented on the issue:
https://github.com/apache/tinkerpop/pull/351
Ok I thought The main point here was robustness in typing for non-java
languages. Hence why I suggested even typing things like Int and using java
classes. Honestly depending on how you compiled your PHP your basic JSON int
will be converted to `Long`. And that's the case I was highlighting.
It makes sense to ignore this if you're trying to reduce de payload but
we'll still be lacking on the non-lossiness end.
>As I see it for how I implemented the TypeDeserializer, it acts as a meta
deserializer that will read the raw text JSON sequentially, so there's no
chance there can be a mixup in the order
You can't guaranty that the order would be maintained in some languages
hence my previous comment. These languages will parse the JSON into `List<Map,
?>` then check the list and Map along the lines of what I said in my previous
post. It would be much more efficient to simply have JSON cast to `Map` and run
a simple check on keys.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
