You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updating a non-string property with a string value changes the value type to string of the property with the following Patch call: /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/$value
To reproduce
Create a submodel with any property that is not a string (double, int, etc..) and update it with the Swagger UI with a string value.
Screenshots
No response
Expected Behaviour
At least, an error should be returned that the value type is not matching. The server, however, could try to parse the string to the expected data type and give an error if that fails. This allows some flexibility.
iosb-ina-mr
changed the title
[Bug]: Updating non-string submodel properties with string values changes their value type
[Bug]: Updating non-string submodel properties with string values changes their value type using the REST API
Apr 11, 2024
Contact Details
marc.riedlinger@iosb-ina.fraunhofer.de
Describe the bug
Updating a non-string property with a string value changes the value type to string of the property with the following Patch call:
/shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/$value
To reproduce
Create a submodel with any property that is not a string (double, int, etc..) and update it with the Swagger UI with a string value.
Screenshots
No response
Expected Behaviour
At least, an error should be returned that the value type is not matching. The server, however, could try to parse the string to the expected data type and give an error if that fails. This allows some flexibility.
Version
Commit: 2c90a7a
Operating System
Linux
Relevant log output
No response
The text was updated successfully, but these errors were encountered: