✨ define deployment-level overrides on native configs: tracking, sync#166
Merged
JGreenlee merged 1 commit intoe-mission:mainfrom Jul 25, 2025
Merged
Conversation
Some behaviors of the native code are configurable via the "tracking" config and "sync" config. Defaults are set in the native code (i.e. app level) and users can edit in Profile > Developer Zone, but up to now they have not been set at the deployment level.
For the fleet version of OpenPATH, we did add support for one deployment-level config option under "tracking" ("bluetooth_only" which mapped to "isFleet" in the native code) but it was handled separately from other options.
We are reworking the native code so that *any* fields defined in "tracking" or "sync" override the built-in default values when that config is constructed.
This brings the deployment config spec in line with the native code spec and should simplify the config logic in the process.
JGreenlee
force-pushed
the
tracking-sync-config-overrides
branch
from
98399f3 to
5e79030
Compare
github-project-automation
bot
moved this from Ready for review by Shankari
to Tasks completed
in OpenPATH Tasks Overview
shankari
pushed a commit
that referenced
this pull request
Oct 13, 2025
…#166) Some behaviors of the native code are configurable via the "tracking" config and "sync" config. Defaults are set in the native code (i.e. app level) and users can edit in Profile > Developer Zone, but up to now they have not been set at the deployment level. For the fleet version of OpenPATH, we did add support for one deployment-level config option under "tracking" ("bluetooth_only" which mapped to "isFleet" in the native code) but it was handled separately from other options. We are reworking the native code so that *any* fields defined in "tracking" or "sync" override the built-in default values when that config is constructed. This brings the deployment config spec in line with the native code spec and should simplify the config logic in the process.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some behaviors of the native code are configurable via the "tracking" config and "sync" config. Defaults are set in the native code (i.e. app level) and users can edit in Profile > Developer Zone, but up to now they have not been set at the deployment level. For the fleet version of OpenPATH, we did add support for one deployment-level config option under "tracking" ("bluetooth_only" which mapped to "isFleet" in the native code) but it was handled separately from other options.
We are reworking the native code so that any fields defined in "tracking" or "sync" override the built-in default values when that config is constructed. This brings the deployment config spec in line with the native code spec and should simplify the config logic in the process.