Add forward compatibility to TaggedFieldSerializer

[causis]

Hello, how do you do?
I was wondering why TaggedFieldSerializer doesn't have a configuration like jackson's "FAIL_ON_UNKNOWN_PROPERTIES". It seems that it would be an easy way to add forward compatibility on demand, and I think the only piece of code that would need to be changed is:

if (cachedField == null) 
  throw new KryoException("Unknown field tag: " + tag + " (" + getType().getName() + ")");

This would give us more flexibility, specially when 2 different apps are used to serialize and deserialize the object.
It would also allow to avoid having to declare deprecated fields, although this could be a dangerous practice, leading to forgetting and reusing a tag.
Thank you very much!

[psmarcos]

+1

[magro]

Pull requests welcome! :-)

Am 01.10.2015 21:41 schrieb "Pablo Marcos" notifications@github.com:

+1

—
Reply to this email directly or view it on GitHub.

[causis]

Great! I'll work on it and send it!
Thanks!

[levyfan]

Hi, I have just sent a pull request. Could you please help review it?

[fgaule]

Would be great to have this feature soon 👍

[magro]

Resolved with #365

[cypherdare]

@levyfan Could you explain why the fields need to be written in tag value order? (Maybe just to make reading faster?) And I don't see where or how the unknown bytes of the future tagged field are skipped in the Input. Thanks.