You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -182,7 +182,9 @@ If you change or remove an existing feature that would lead to a breaking change
182
182
- Use a default value that falls back to existing behavior.
183
183
- Add a deprecation definition in `Deprecator/Deprecations.js` that will output a deprecation warning log message on Parse Server launch, for example:
184
184
> DeprecationWarning: The Parse Server option 'example' will be removed in a future release.
185
-
185
+
186
+
For deprecations that can only be determined ad-hoc during runtime, for example Parse Query syntax deprecations, use the `Deprecator.logRuntimeDeprecation()` method.
187
+
186
188
Deprecations become breaking changes after notifying developers through deprecation warnings for at least one entire previous major release. For example:
187
189
-`4.5.0` is the current version
188
190
-`4.6.0` adds a new optional feature and a deprecation warning for the existing feature
0 commit comments