-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Explicitly mention string-dedent as the current polyfill? #80
Comments
It’s only stage 2, there really shouldn’t be any polyfills yet. |
As I said in my original issue:
Polyfill or not, there appears to exist a library that matches this proposal - happy to use another term to refer to it; though my impression overall is that this is primarily waiting for reviewers to sign off / champions to re-present more than anything |
Err, that's not how I interpreted https://tc39.es/process-document under Implementation Types Expected* for stage 1. The asterisk there is * This column does not indicate a requirement for advancement, but simply a general expectation. Is there more detail mentioned anywhere in TC39 docs around polyfill timing? If there is and it's contrary to that process document I can file an issue / send a docs PR. |
No, and attempts to refine this have received pushback - i already have an open PR. To be clear, a package that matches the proposal without mutating builtins is fine at any stage - it’s just that before stage 3, the shape may change at any time, often drastically. Although i use the term “polyfill” to mean such a function and “shim” to mean a self-installing one, enough people still assume the term polyfill includes the self-installation (which is the problematic part). |
👋 I'm the proposal champion and author of |
Coming over from dmnd/dedent#76, @G-Rath mentioned that
string-dedent
is used in the REPL. I don't that package or the word "polyfill" mentioned anywhere else in the proposal.Could
string-dedent
be mentioned in the README.md as the current polyfill for the package? Right now it's unclear what folks would want to be using for the current proposal's behavior.The text was updated successfully, but these errors were encountered: