Skip to content
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

Check-in Location Update: Correct Behavior #54

Open
toadzky opened this issue Apr 18, 2020 · 0 comments
Open

Check-in Location Update: Correct Behavior #54

toadzky opened this issue Apr 18, 2020 · 0 comments
Labels
bug Something isn't working Devices Related to the Devices API

Comments

@toadzky
Copy link
Contributor

toadzky commented Apr 18, 2020

Right now, the endpoint just sets the provided lat/long on the check-in.

The correct process, as defined by product, is:

  1. Get the lat/long of the scannable's site.
  2. If site has no location, do nothing.
  3. Compare provided lat/long and site's lat/long..
  4. If within some configurable range...
    1. copy the site's lat/long to the scan relationship
    1. set the verified flag property to true on the scan relationship
  5. Else, set the verified flag property to false on the scan relationship
@toadzky toadzky added bug Something isn't working Devices Related to the Devices API labels Apr 25, 2020
@toadzky toadzky added this to the V2 - Self-reporting API milestone Apr 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Devices Related to the Devices API
Projects
None yet
Development

No branches or pull requests

1 participant