Update README to match the new code #1064
Conversation
This should match better with the code after microsoft#1034.
|
Thanks for the PR! This section of the codebase is owned by @saschanaz - if they write a comment saying "LGTM" then it will be merged. |
|
|
||
| ### What are the TypeScript team's heuristics for PRs to the DOM APIs | ||
|
|
||
| Changes to this repo can have pretty drastic ecosystem effects, because these types are included by default in TypeScript. |
There was a problem hiding this comment.
This paragraph is mostly still true, right? I know we are less conservative than before, but the idea is that every update to @types/web will eventually ship with Typescript by default means that there are some changes that will not be OK until there's a way to publish other packages from here.
There was a problem hiding this comment.
Yes, maybe it's good to keep the sentence for maintainers. It has minimal meaning for contributors though, since nearly all changes will now be from webref and MDN rather than manual PRs.
There was a problem hiding this comment.
I know we are less conservative than before
I'm not sure, as quite a lot types are removed for lack of broad browser support?
Co-authored-by: Nathan Shively-Sanders <[email protected]>
|
Cool, I'd like to merge this if @sandersn also agrees. |
|
LGTM |
|
Merging because @saschanaz is a code-owner of all the changes - thanks! |
This should match better with the code after #1034.