Skip to content
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

[popover2] feat: export DefaultPopover2TargetHTMLProps #5735

Merged
merged 2 commits into from
Nov 9, 2022

Conversation

adidahiya
Copy link
Contributor

Alternative to #5734, which did not work...

Changes proposed in this pull request:

It turns out #5713 also had a typings regression for the popoverRef prop on datetime2 & select components, specifically the bit with React.HTMLProps<unknown>. In trying to improve this type definition, I found myself writing React.HTMLProps<HtmlElement> in a lot of places, since that's the default assumed in the definition of Popover2Props<T = ...>. That's now fixed in the public API of @blueprintjs/popover2 with the new type DefaultPopover2TargetHTMLProps.

changelog:

  • feat: export new type DefaultPopover2TargetHTMLProps
  • fix(DateInput2, DateRangeInput2): type definition of popoverRef prop is now usable in most cases without type casting
  • fix(Select2, Suggest2, MultiSelect2): type definition of popoverRef prop no longer has the regression introduced in v4.8.8 with [select,datetime2] support popoverProps.targetTagName #5713

@blueprint-bot
Copy link

add explanation to Popover2 docs

Previews: documentation | landing | table | demo

@adidahiya adidahiya merged commit 15c7125 into develop Nov 9, 2022
@adidahiya adidahiya deleted the ad/fix-select-datetime-popover-type branch November 9, 2022 01:00
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