-
Notifications
You must be signed in to change notification settings - Fork 35
Have location tracking in mobile-config track #1010
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
Conversation
|
|
||
| if self.asserted_location != radio.location { | ||
| self.asserted_location = radio.location; | ||
| self.asserted_location_changed_at = Some(radio.refreshed_at); |
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.
WDYT @bbalser Should we update last_changed_at here?
self.last_changed_at = radio.refreshed_at;
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.
It makes sense to me since we're changing something about the radio. Unless last_changed_at is used for something other than change tracking.
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, but on the other hand, we're tracking location and the time it changed separately, so that's why I'm not sure what the best option is here.
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.
yes, I think we do
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.
Added
Previous (duplicate) PR: #907
Add migration to back fill data.
usage
./target/debug/mobile-config -c mobile-config.toml migrate-mobile-tracker file.csv