> older versions used to deserialize to the minimum needed type, i.e. 1 will > get deserialized as 1 instead of 1.0; now 1 and 1.0 will be deserialized as > 1.0
Learned something new again. No way to configure GSON to revert to the old behaviour? > When the service becomes stable, it is quite possible much of the parsing > logic can be eliminated (especially if the JSON gets restructured). Fair point. Could we add a code comment then to document that the parsing logic should be revisited if and when the JSON representation settles down? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/39#issuecomment-27344222
