Skip to content

Invalid backward compatibility result for new read-only property in PUT operations #136

Closed
@trohrberg

Description

@trohrberg

Hi, thank you for creating this tool which helps us a lot in our project. We noticed the following deviation between the tool's responses concerning backward compatibility and our expectation. I would like to discuss that here to see if you agree with our perspective:

We consider the addition of a new read-only property into an API model as a breaking change for PUT operations. A client not knowing of the new read-only property would get a resource from the API which includes the new read-only property and would send a full update back via PUT omitting that new property. The result is that the property would be cleared on the server side as the client did not sent the retrieved value back.

I will shortly provide a pull request fixing this issue (if it is one) and appreciate a lot your comments and opinions on whether this is an issue or not.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions