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
{{ message }}
Repository navigation
Consider removing extensions to prototypes of base types in favor of custom functions #18871
We're editing the String interface itself by extending String.prototype, the issue with that is that other extensions which might share the same typing names might override our prototypes, for eg. fileToCommandArgument() also exists in Jupyter extension.
Convert all these to functions similar to like we have done with asyncFilter.
changed the title [-]Convert typings in `extensions.ts` to functions[/-][+]Consider removing extensions to prototypes of base types in favor of custom functions[/+]on Apr 7, 2022
Activity
[-]Convert typings in `extensions.ts` to functions[/-][+]Consider removing extensions to prototypes of base types in favor of custom functions[/+]lucyydotp commentedon Jan 25, 2023
+1 for this, especially for
replaceAllwhich is now standard and is breaking other pluginsMove `replaceAll` and `splitLines` out of string extensions. (#20626)
Merge remote-tracking branch 'upstream/main'
Merge remote-tracking branch 'upstream/main'