refactor(analytics): default config for forex_enabled #7695
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.
Type of Change
Description
Currently, if the
forex_enabled
feature flag is not present as an ENV, it is leading to deserialization errors.Modified it in such a way to assume the default value (false) if the ENV is not present.
Additional Changes
Motivation and Context
Fix deserialization errors for analytics
How did you test it?
Removed the

forex_enabled
feature flag from local envs, and replicated the errorNeed to remove the env

forex_enabled
during deployment, and then test out the analytics section..Tested on local, by removing the
forex_enabled
env and checking the analytics API calls, worked as expectedCurl:
Checklist
cargo +nightly fmt --all
cargo clippy