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
If your code (or library code) is using a feature support test conditional statement before using a feature, then you still get an error reported by this plugin. It doesn't know your intent when doing such checks.
Could this plugin make guesses of reasonable confidence that statements like the following should not cause an error?
I think in order to reliably determine the method existence check, we need to analyze the code path and identify where the code is placed. I think it's very difficult to do, but if you have ideas please comment here or open a PR to add changes.
if(String.prototype.replaceAll){// use replaceAll}if(!String.prototype.replaceAll){// use polyfill}else{// use replaceAll}if(typeofString.prototype.replaceAll!=='undefined'){// use replaceAll}if(typeofString.prototype.replaceAll==='undefined'){// use polyfill}else{// use replaceAll}a=String.prototype.replaceAll ? /* use replaceAll */ : /* use polyfill */;
If your code (or library code) is using a feature support test conditional statement before using a feature, then you still get an error reported by this plugin. It doesn't know your intent when doing such checks.
Could this plugin make guesses of reasonable confidence that statements like the following should not cause an error?
This issues arises from robatwilliams/es-compat#72
The text was updated successfully, but these errors were encountered: