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
Add default remote keys for all feature flags #1716
Comments
@bjtitus I think there's one additional test we should do:
|
Are you saying we should store the changed Remote Config value instead of reverting to the value in Is the idea to cover future flag removal? I fear this could make it much hard for us to debug issues without knowing which flag values a user should have. As an example, if someone accidentally added a flag and then deleted it, would we be able to determine which value a user should have on their device without needing to fetch logs/data directly from them? If we do decide to do this, I think it should be done separately from the default values since this would be new functionality on top of just adding a default value for each flag. |
Yes! My main reasoning is: that if an app is working with a flag set to a certain value, it should not change. Think about this scenario:
I agree with you but overall in support requests one of the things we always recommend is to be on the latest version — but I also agree that this is an argument that goes both ways.
In terms of implementation wouldn't that be just a matter of settings flags values only from the list that is returned from the backend? So in case |
Yeah, the implementation isn't too bad, I just wanted to make sure it's easily revertible if we end up with issues. I think having a separate commit is fine: 0f4659e |
Description
Any feature flag we add currently needs a corresponding
remoteKey
added.We shouldn't need to do this since any flag should be overridable server side for flexibility.
Step-by-step reproduction instructions
FeatureFlag.swift
Screenshots or screen recording
No response
Did you search for existing bug reports?
Device, Operating system, and Pocket Casts app version
No response
The text was updated successfully, but these errors were encountered: