Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat(select): Convert JS to TypeScript #4386
feat(select): Convert JS to TypeScript #4386
Changes from 1 commit
9313e66
135e09d
bc8bf0d
fb0b996
7a7d960
91f5975
b50a47a
01edf0f
a286663
5facf07
7b625f6
f6de964
4fa0e79
dc34eb6
de38dd6
01b22be
ebbbbb9
a236050
1e8b7e2
a0cce8c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it guaranteed that this will always be HTMLElement? I think so, but just wondering what you were thinking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was because we're calling
.focus()
on these items in a few places, and I assumed.mdc-list-item
would always be anHTMLElement
anyway, so I thought we could avoid type assertions by just declaring it anHTMLElement
.However, it looks like it's pretty easy to change this back to
Element
if you prefer (take a look at commit 91f5975).I figured it's probably OK to return a more specific subtype, as long as our arguments are still
Element
for Closure users.WDYT?