Skip to content

Remove redundant added types #647

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

Merged
merged 3 commits into from
Apr 3, 2019
Merged

Conversation

saschanaz
Copy link
Contributor

@saschanaz saschanaz commented Jan 29, 2019

  1. ElementCreationOptions is already in IDL
  2. ParentNode is already in IDL
  3. BroadcastChannelEventMap is already defined elsewhere (we currently have two of them)
  4. NodeSelector has been merged into ParentNode and is not used anymore

ImageBitmapOptions is covered by #571.

@sandersn sandersn merged commit 4752f02 into microsoft:master Apr 3, 2019
@saschanaz saschanaz deleted the cleanup2 branch April 4, 2019 11:49
dbjorge added a commit to microsoft/accessibility-insights-web that referenced this pull request Aug 14, 2019
…cript upgrade (#1065)

Updating from Typescript 2.9 to 3.5 results in a variety of errors that look like this:

```
ERROR in Q:/repos/accessibility-insights-web/src/common/document-manipulator.ts(4,42):
TS2304: Cannot find name 'NodeSelector'.
```

It looks like microsoft/TypeScript-DOM-lib-generator#647 was the point where it was removed, merged into a separate `ParentNode` interface. We considered using `ParentNode` instead here, but `Document` seemed closer to the intended usage in most cases and led to the tests working more similarly to the product code than anything else, so that's what I went with.

Replacing the usages with Document is a no-op in Typescript 2.9 (so nice to do as a separate PR, to make the eventual Typescript upgrade PR smaller). It also forces the affected tests to be a little bit better (they create test documents for the cases where the product passes real documents, rather than creating test nodes within a global document and hoping that they act similarly and that no other test touches global document state).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants