-
Notifications
You must be signed in to change notification settings - Fork 33
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
device-reachability-status
& device-roaming-status
: Alignment of errors with Commonalities
#183
device-reachability-status
& device-roaming-status
: Alignment of errors with Commonalities
#183
Conversation
device-reachability-status
& device-roaming-status
: Alignment of errors with Commonalities
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM @maxl2287 thanks
One issue: the changelog in the PR itself mention geofencing ;) - easy fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maxl2287 checking with my own yaml.
Seems that the 422 with error code UNSUPPORTED_DEVICE_IDENTIFIERS
is missing.
Check case 1 https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#62-error-responses---device-object
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Alignement of errors according to Commonalities guideline.
Which issue(s) this PR fixes:
Fixes #180 #181
Special notes for reviewers:
Changelog input