-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Labels
bounty:$50Bounty applies for fixing this issue (Parse Bounty Program)Bounty applies for fixing this issue (Parse Bounty Program)state:releasedReleased as stable versionReleased as stable versionstate:released-alphaReleased as alpha versionReleased as alpha versionstate:released-betaReleased as beta versionReleased as beta versiontype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
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
Metadata
Metadata
Assignees
Labels
bounty:$50Bounty applies for fixing this issue (Parse Bounty Program)Bounty applies for fixing this issue (Parse Bounty Program)state:releasedReleased as stable versionReleased as stable versionstate:released-alphaReleased as alpha versionReleased as alpha versionstate:released-betaReleased as beta versionReleased as beta versiontype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature