-
Notifications
You must be signed in to change notification settings - Fork 0
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
Features/configure response #62
Conversation
return requested_g | ||
# if max if "boolean" nothing else is permitted | ||
if max_g == GRANULARITY_BOOLEAN: | ||
return max_g |
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.
so if the user (with boolean access only) requests full records, they get back booleans and not an error? does the spec have an opinion on this or is it a free-for-all?
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.
Yeah, it's a free-for-all, although I am mostly following the suggestion here in the spec. Since we can do whatever, we could also:
- return 401 Unauthorized (or 400 Bad Request?)
- return as in this pr, but add a message in the response along the lines of "you don't have permissions for this granularity"
I think either of these is fine.
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.
yeah based on the spec I think this is good then!
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
(Requires bento repo changes here to run)
Large refactor of beacon response code.