-
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
Update device error model #232
base: main
Are you sure you want to change the base?
Update device error model #232
Conversation
@fernandopradocabrillo Agree with you to keep it but in order to be explicit the code should not be: |
Hi @fernandopradocabrillo
Following points are open:
|
I'm not sure, I see that in geofencing it is also SUBSCRIPTION_MISMATCH: https://github.com/camaraproject/DeviceLocation/blob/main/code/API_definitions/geofencing-subscriptions.yaml#L1166 do you know if there is any conversation right now in commonalities regarding the errors in subscriptions? |
@fernandopradocabrillo would it be possible to cover the 2 new APIs here as well? 🙂 (connected-network-type-subscriptions is still to be merged) |
…into update-device-error-model
yeah and I won't charge extra |
@camaraproject/device-status_maintainers shouldn't the POST /subscription endpoint also have the 404 IDENTIFIER_NOT_FOUND error? |
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Align error model with Commonalities for meta Spring25
Which issue(s) this PR fixes:
Fixes #230
Special notes for reviewers:
In the subscriptions APIs there is one error that I'm not sure if we have to update or not.
It looks like it is the equivalent to
403 INVALID_TOKEN_CONTEXT
. It may make sense to keep it since thedevice
object is required when creating the subscription, regardless of the token type. I tend to think we should keep it.