Older client exceptions when accessing newer API #7
Comments
|
This is happening again with a change from early 9.1 to 9.2.5. The DNSZone objects now have a displayName property which is causing an exception: A better way of dealing with this needs to be devised. |
ewannema
pushed a commit
that referenced
this issue
Jan 13, 2020
Attributes that the server sends, but the local API definition is not aware of will be ignored. This should allow for some forward compatibility as long as the new attributes are not required. This issue stems from the design goal of minimizing dependencies which eliminated the option of parsing the WSDL at runtime. This is not an ideal solution - realistically, I would recommend the M&M provided REST API now that it is available.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The 0.1.0 client is exceptioning when accessing a newer API version.
[undefined 'method last_modified=' for #<MmJsonClient::DNSZone:0x0000000000d561c8>]It is expected that items added to the API would not be available in the older version and that there would be errors if the API for existing items changed (property/method removal), but I would not expect the client to be blowing up when there are new properties exposed. This could be an issue for minor updates of M&M.
This ticket is to determine if we can change the behavior and allow the older API to still work against the newer version for common methods/properties.
The text was updated successfully, but these errors were encountered: