-
Notifications
You must be signed in to change notification settings - Fork 8
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
Swagger Definition and Response of the endpoint get /states are not matching #95
Comments
…states is a dictionary a not a list. Change Swagger Response to Dictionary
Hey, thank you for reporting. You now created a fork and did your commit and so you can open your branch https://github.com/jkuenemund/ioBroker.rest-api/tree/swagger_yaml_get_states_wrong_response and you should have a "create PR" (or was it called "contribute") and with this you create PullRequest |
Hi, thanks for your response. I created a PullRequest (#96) hopefully with the correct target branch. |
yes looks good, perfekt. |
Describe the bug
The current swagger definition for the endpoint get /states describes the Response as an array of states, with that an example of a response is:
[ { "id": "string", "val": "string", "q": 0, "ts": 0, "lc": 0, "ack": true, "from": "string", "expire": 0, "type": "string", "common": {}, "native": {} } ]
.But the real response is more looking like
[ "adapter.0.name.value": { "id": "string", "val": "string", "q": 0, "ts": 0, "lc": 0, "ack": true, "from": "string", "expire": 0, "type": "string", "common": {}, "native": {} } ]
.With that the Response is a map (or dictionary) and not a list.
To Reproduce
Steps to reproduce the behavior:
Call the get /states endpoint.
The text was updated successfully, but these errors were encountered: