We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
query ($device_id: ID!) { device(id: $device_id) { hostname: name } }
along with one of your device's UUID as the query.
Expect to see the device's hostname returned.
Get error with following:
{ "errors": [ { "message": "'Device' object has no attribute 'only'", "locations": [ { "line": 2, "column": 3 } ], "path": [ "device" ] } ], "data": { "device": null } }
A larger query returns this:
{ "errors": [ { "message": "'Device' object has no attribute 'select_related'", "locations": [ { "line": 2, "column": 3 } ], "path": [ "device" ] } ], "data": { "device": null } }
This appears to be related to optimizations that were done in the core.
The text was updated successfully, but these errors were encountered:
Probably a regression introduced by #769.
Sorry, something went wrong.
Seems to be specifically an issue with "single" queries (e.g. device as opposed to devices.) The corresponding devices query seems to work fine:
device
devices
query ($device_id: String!) { devices (id: [$device_id]) { hostname: name } }
Fix #1112: correct bad logic in optimization of single-object GraphQL…
07eb165
… endpoints
295796c
… endpoints (#1120)
glennmatthews
Successfully merging a pull request may close this issue.
Environment
Steps to Reproduce
along with one of your device's UUID as the query.
Expected Behavior
Expect to see the device's hostname returned.
Observed Behavior
Get error with following:
A larger query returns this:
This appears to be related to optimizations that were done in the core.
The text was updated successfully, but these errors were encountered: