Skip to content
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.

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

[Bug]: Updating non-string submodel properties with string values changes their value type using the REST API #236

Open
iosb-ina-mr opened this issue Apr 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@iosb-ina-mr
Copy link

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

@iosb-ina-mr iosb-ina-mr added the bug Something isn't working label Apr 11, 2024
@iosb-ina-mr 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant