feat: Add Cloud Code triggers Parse.Cloud.beforeSave and Parse.Cloud.afterSave for Parse Config#9232
Merged
mtrezza merged 3 commits intoparse-community:alphafrom Jul 20, 2024
Conversation
Thanks for opening this pull request! |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## alpha #9232 +/- ##
==========================================
+ Coverage 93.75% 93.76% +0.01%
==========================================
Files 184 184
Lines 14675 14715 +40
==========================================
+ Hits 13758 13797 +39
- Misses 917 918 +1 ☔ View full report in Codecov by Sentry. |
mtrezza
approved these changes
Jul 20, 2024
mtrezza
changed the title
mtrezza
changed the title
Parse.Cloud.beforeSave and Parse.Cloud.afterSave for Parse Config
Member
|
Nice! |
parseplatformorg
pushed a commit
that referenced
this pull request
Jul 20, 2024
# [7.3.0-alpha.6](7.3.0-alpha.5...7.3.0-alpha.6) (2024-07-20) ### Features * Add Cloud Code triggers `Parse.Cloud.beforeSave` and `Parse.Cloud.afterSave` for Parse Config ([#9232](#9232)) ([90a1e4a](90a1e4a))
Contributor
|
🎉 This change has been released in version 7.3.0-alpha.6 |
7 tasks
parseplatformorg
pushed a commit
that referenced
this pull request
Oct 3, 2024
# [7.3.0-beta.1](7.2.0...7.3.0-beta.1) (2024-10-03) ### Bug Fixes * Custom object ID allows to acquire role privileges ([GHSA-8xq9-g7ch-35hg](GHSA-8xq9-g7ch-35hg)) ([#9317](#9317)) ([13ee52f](13ee52f)) * Parse Server `databaseOptions` nested keys incorrectly identified as invalid ([#9213](#9213)) ([77206d8](77206d8)) * Parse Server installation fails due to post install script incorrectly parsing required min. Node version ([#9216](#9216)) ([0fa82a5](0fa82a5)) * Parse Server option `maxLogFiles` doesn't recognize day duration literals such as `1d` to mean 1 day ([#9215](#9215)) ([0319cee](0319cee)) * Security upgrade path-to-regexp from 6.2.1 to 6.3.0 ([#9314](#9314)) ([8b7fe69](8b7fe69)) ### Features * Add atomic operations for Cloud Config parameters ([#9219](#9219)) ([35cadf9](35cadf9)) * Add Cloud Code triggers `Parse.Cloud.beforeSave` and `Parse.Cloud.afterSave` for Parse Config ([#9232](#9232)) ([90a1e4a](90a1e4a)) * Add Node 22 support ([#9187](#9187)) ([7778471](7778471)) * Add support for asynchronous invocation of `FilesAdapter.getFileLocation` ([#9271](#9271)) ([1a2da40](1a2da40))
Contributor
|
🎉 This change has been released in version 7.3.0-beta.1 |
parseplatformorg
pushed a commit
that referenced
this pull request
Oct 3, 2024
# [7.3.0](7.2.0...7.3.0) (2024-10-03) ### Bug Fixes * Custom object ID allows to acquire role privileges ([GHSA-8xq9-g7ch-35hg](GHSA-8xq9-g7ch-35hg)) ([#9317](#9317)) ([13ee52f](13ee52f)) * Parse Server `databaseOptions` nested keys incorrectly identified as invalid ([#9213](#9213)) ([77206d8](77206d8)) * Parse Server installation fails due to post install script incorrectly parsing required min. Node version ([#9216](#9216)) ([0fa82a5](0fa82a5)) * Parse Server option `maxLogFiles` doesn't recognize day duration literals such as `1d` to mean 1 day ([#9215](#9215)) ([0319cee](0319cee)) * Security upgrade path-to-regexp from 6.2.1 to 6.3.0 ([#9314](#9314)) ([8b7fe69](8b7fe69)) ### Features * Add atomic operations for Cloud Config parameters ([#9219](#9219)) ([35cadf9](35cadf9)) * Add Cloud Code triggers `Parse.Cloud.beforeSave` and `Parse.Cloud.afterSave` for Parse Config ([#9232](#9232)) ([90a1e4a](90a1e4a)) * Add Node 22 support ([#9187](#9187)) ([7778471](7778471)) * Add support for asynchronous invocation of `FilesAdapter.getFileLocation` ([#9271](#9271)) ([1a2da40](1a2da40))
Contributor
|
🎉 This change has been released in version 7.3.0 |
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
3 participants
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.
Pull Request
Issue
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.
Closes: #8267
Approach
Add a Cloud Code trigger beforeSave and afterSave that is invoked when the remove config is changed. This allows a developer to catch any changes to the Remote Config parameters and log them, or store a history of changed.
Tasks