Conversation
Codecov Report
@@ Coverage Diff @@
## master #7303 +/- ##
==========================================
- Coverage 93.93% 86.26% -7.67%
==========================================
Files 179 181 +2
Lines 13153 13190 +37
==========================================
- Hits 12355 11379 -976
- Misses 798 1811 +1013
Continue to review full report at Codecov.
|
|
I changed the log message from
to
This is according to the Node.js deprecation warnings and makes it easier so search log files by term |
|
@dplewis If there is no objection, I'll merge this later today. The coverage change is actually 0%; just with the last commit it seems that cov is reporting false negatives. |
* adds deprecator * un-fit * added changelog entry * some fixes * un-fit * removed deprecation definition * changed deprecation log syntax according to Nodejs
|
🎉 This change has been released in version 5.0.0-beta.1 |
|
🎉 This change has been released in version 5.0.0 |
New Pull Request Checklist
Issue Description
Currently, there is no mechanism provided to deprecate Parse Server settings.
Related issue: closes #7302
Approach
Adds a new
Deprecatorin./Deprecatordirectory.Features:
./Deprecator/Deprecations.jsin a standardized way tonew ParseServer(...))Examples
someFeatureoption default will change fromfalsetotrue:someFeatureoption name will change tosomethingElse:someFeatureoption name will be removed:TODOs before merging
[ ] Add changes to documentation (guides, repository pages, in-code descriptions)to be added in Add deprecation policy #7199