location: make accuracy default config floats
previously they were ints which could possibly break caching with cachew
This commit is contained in:
parent
8addd2d58a
commit
f3507613f0
2 changed files with 2 additions and 2 deletions
|
@ -25,7 +25,7 @@ class Config(user_config):
|
|||
# default ~30km accuracy
|
||||
# this is called 'home_accuracy' since it lives on the base location.config object,
|
||||
# to differentiate it from accuracy for other providers
|
||||
home_accuracy: float = 30_000
|
||||
home_accuracy: float = 30_000.0
|
||||
|
||||
# TODO could make current Optional and somehow determine from system settings?
|
||||
@property
|
||||
|
|
|
@ -28,7 +28,7 @@ class semantic_locations_config(user_config.google_takeout_semantic):
|
|||
# https://locationhistoryformat.com/reference/semantic/#/$defs/placeVisit/properties/locationConfidence
|
||||
require_confidence: int = 40
|
||||
# default accuracy for semantic locations
|
||||
accuracy: float = 100
|
||||
accuracy: float = 100.0
|
||||
|
||||
|
||||
config = make_config(semantic_locations_config)
|
||||
|
|
Loading…
Add table
Reference in a new issue