-
Notifications
You must be signed in to change notification settings - Fork 23
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
Have location tracking in mobile-config track #907
base: main
Are you sure you want to change the base?
Conversation
758bdaf
to
02a3651
Compare
@@ -86,17 +88,23 @@ impl TrackedMobileRadio { | |||
hash: radio.hash(), | |||
last_changed_at: radio.refreshed_at, | |||
last_checked_at: Utc::now(), | |||
asserted_location: radio.location, | |||
asserted_location_change_at: None, |
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.
What is the thinking about making this None? The first time we see a radio, this field will be null and how do you envision clients working with it?
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.
What is the thinking about making this None?
My logic is next: At the beginning it is None because we don't have information about previous time when asserted_location was changed.
The first time we see a radio, this field will be null and how do you envision clients working with it?
I expect clients (or functions that use tracked mobile radio table) will handle None by their own logic.
Otherwise, if we hardcode some value here, we don't give an option for the clients.
Additional feature to previous PR: #902