Correct behavior of PATCH /submodel/$value #160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

arnoweiss opened this issue Aug 23, 2023 · 0 comments

Assignees

Labels

Milestone

arnoweiss commented Aug 23, 2023

Let's say there's a Submodel with a SubmodelElementList. This SMEL has 10 entries.
This submodel receives a PATCH /submodel/$value with a payload that has 15 entries of the same structure for the SMEL.

What's the intended behavior here?

HTTP 204 --> all 15 SMEL-entries are deserialized into full AAS-objects and then replace the previous 10 entries.
HTTP 400 --> The size of the SMELs does not match. The server has no full AAS-objects to deserialize the last 5 entries into.

The text was updated successfully, but these errors were encountered:

arnoweiss changed the title ~~Correct behavior of PATCH/submodel/$value~~ Correct behavior of PATCH /submodel/$value

sebbader-sap self-assigned this

sebbader-sap added this to the 3.1 milestone

sebbader-sap added the documentation label

sebbader-sap mentioned this issue

Patch Clarifications #312

Draft

sebbader-sap modified the milestones: 3.1, 3.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment