-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 remote config history #2339
Labels
bounty:$50
Bounty applies for fixing this issue (Parse Bounty Program)
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:feature
New feature or improvement of existing feature
Comments
Thanks for opening this issue!
|
mtrezza
added
type:feature
New feature or improvement of existing feature
bounty:$50
Bounty applies for fixing this issue (Parse Bounty Program)
labels
Nov 1, 2022
u mean this one right? https://github.com/parse-community/parse-dashboard/blob/alpha/src/dashboard/Data/Config/Config.react.js. The "Dynamically configure your app" section of parse dashboard right? @mtrezza |
Yes |
4 tasks
🎉 This change has been released in version 6.0.0-alpha.7 |
🎉 This change has been released in version 6.0.0-beta.2 |
🎉 This change has been released in version 6.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bounty:$50
Bounty applies for fixing this issue (Parse Bounty Program)
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:feature
New feature or improvement of existing feature
New Feature / Enhancement Checklist
Current Limitation
When changing any value in Remote Config, the previous value is lost without any possibility to undo the change. That means that any user mistake can lead to information irreversibly lost.
Feature / Enhancement Description
Add a history of the remove config changes. The feature in its most basic form should allow to see a history of previous values. In a more advanced form it could allow to roll back to previous values.
The remote config history could be stored locally on the browser side as a basic functionality. As an improvement, the config history should be stored server side, see #2555.
Example Use Case
n/a
Alternatives / Workarounds
Implement a custom solution in Cloud Code trigger (this requires feature parse-community/parse-server#8267 to be implemented)
3rd Party References
The text was updated successfully, but these errors were encountered: