@@ -198,6 +198,29 @@ from a pull request on the outdated vendor). This mode allows you to
198
198
ignore those deprecations, allowing you to notice when *your code * is
199
199
using deprecated APIs, and to keep up with the changes.
200
200
201
+ Here is a summary that should help you pick the right mode:
202
+
203
+ +------------------------+-----------------------------------------------------+
204
+ | Mode | Recommended situation |
205
+ +========================+=====================================================+
206
+ | strict | Recommended for actively maintained projects |
207
+ | | with little to no dependencies |
208
+ +------------------------+-----------------------------------------------------+
209
+ | <some integer> | Recommended for projects that you cannot |
210
+ | | immediately fix but don't want to make worse. |
211
+ | | Can be used to transition from one mode to another. |
212
+ +------------------------+-----------------------------------------------------+
213
+ | allow_outdated_vendors | Recommended for projects with dependencies |
214
+ | | that fail to keep up with new deprecations. |
215
+ +------------------------+-----------------------------------------------------+
216
+ | weak_vendors | Recommended for libraries that use |
217
+ | | the deprecation system themselves and |
218
+ | | cannot afford to use one of the modes above. |
219
+ +------------------------+-----------------------------------------------------+
220
+ | weak | Not recommended; will probably lead to |
221
+ | | a big refactoring. |
222
+ +------------------------+-----------------------------------------------------+
223
+
201
224
Disabling the Deprecation Helper
202
225
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
203
226
0 commit comments