google / google/closure-compiler
Create written policy for managing externs definitions
Open
internal-issue-created
triage-done
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 1.2k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 6
Description
Internal version of this issue is http://b/124762327
We should have an externally-visible policy for externs definitions to answer questions like these.
1. How "standardized" does a feature have to be before we agree to add externs definitions for it?
2. When do we drop obsolete features from polyfills?
3. How do we handle updates to polyfills that make them more correct, but will break some users?
4. What tricks have we learned about the way to structure externs to avoid compatibility problems?
Contributor guide
Assessment
This issue has not been assessed yet.