I would not change anything in the status code to be backward compatible. I would add a “Warning” header in the response : Warning: 299 – “Deprecated API” You can also specify the “-” with the “Agent” that emits the warning, and be more explicit in the warn-text : Warning: 299 api.blazingFrog.com “Deprecated API: use … Read more
According to Material-ui changelog, it should be solve in V5, which is still in alpha. It seems that at least in some cases this issue cause by createMuiTheme. You can solve this issue by using the experimental (unstable) theme creator If you want to get the experimental theme creator instead of removing React.StrictMode, you can … Read more
You can do it in code by calling the following functions. error_reporting(E_ERROR | E_WARNING | E_PARSE | E_NOTICE); or error_reporting(E_ALL ^ E_DEPRECATED);
You can use JSDoc comments to mark deprecated code: /** * @deprecated The method should not be used */ export const oldFunc = () => {} Also, this eslint rule can look through the deprecated methods and warn about their usage.
Documenting in detail for future readers: The short answer is you need to override both the methods. The shouldOverrideUrlLoading(WebView view, String url) method is deprecated in API 24 and the shouldOverrideUrlLoading(WebView view, WebResourceRequest request) method is added in API 24. If you are targeting older versions of android, you need the former method, and if … Read more
Use addDrawerListener() instead.