[8.17] Update @elastic/ml-ui dependencies (main) (#204210) #207794
Merged
+54
−75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@types/he](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/he) ([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/he)) | devDependencies | minor | [`^1.1.1` -> `^1.2.3`](https://renovatebot.com/diffs/npm/@types%2fhe/1.1.1/1.2.3) | | [react-popper-tooltip](https://togithub.com/mohsinulhaq/react-popper-tooltip) | dependencies | major | [`^3.1.1` -> `^4.4.2`](https://renovatebot.com/diffs/npm/react-popper-tooltip/3.1.1/4.4.2) | --- ### Release Notes <details> <summary>mohsinulhaq/react-popper-tooltip (react-popper-tooltip)</summary> ### [`v4.4.2`](https://togithub.com/mohsinulhaq/react-popper-tooltip/releases/tag/v4.4.2): Fix missing hover check in interactive mode [Compare Source](https://togithub.com/mohsinulhaq/react-popper-tooltip/compare/v4.4.1...v4.4.2) Thanks, [@&elastic#8203;cgsdev0](https://togithub.com/cgsdev0) [https://github.com/mohsinulhaq/react-popper-tooltip/pull/156](https://togithub.com/mohsinulhaq/react-popper-tooltip/pull/156) ### [`v4.4.1`](https://togithub.com/mohsinulhaq/react-popper-tooltip/releases/tag/v4.4.1): Fix unintentional dependency change [Compare Source](https://togithub.com/mohsinulhaq/react-popper-tooltip/compare/v4.4.0...v4.4.1) Thanks [@&elastic#8203;JohnDaly](https://togithub.com/JohnDaly) ### [`v4.4.0`](https://togithub.com/mohsinulhaq/react-popper-tooltip/releases/tag/v4.4.0): Add double click trigger, improve styles declaration, ability to change default tooltip text color [https://github.com/mohsinulhaq/react-popper-tooltip/pull/148](https://togithub.com/mohsinulhaq/react-popper-tooltip/pull/148) [https://github.com/mohsinulhaq/react-popper-tooltip/pull/149](https://togithub.com/mohsinulhaq/react-popper-tooltip/pull/149) [https://github.com/mohsinulhaq/react-popper-tooltip/pull/154](https://togithub.com/mohsinulhaq/react-popper-tooltip/pull/154) ### [`v4.3.0`](https://togithub.com/mohsinulhaq/react-popper-tooltip/releases/tag/v4.3.0): Add Shadow DOM support [Compare Source](https://togithub.com/mohsinulhaq/react-popper-tooltip/compare/v4.2.0...v4.3.0) As pointed out by [https://github.com/mohsinulhaq/react-popper-tooltip/issues/133](https://togithub.com/mohsinulhaq/react-popper-tooltip/issues/133) (thanks [@&elastic#8203;shovalk](https://togithub.com/shovalk)), interactions with the tooltip when rendered using Shadow DOM wasn't working properly. This release adds support for that by using [Event.composedPath](https://developer.mozilla.org/en-US/docs/Web/API/Event/composedPath) to get event target, with `event.target` as fallback for IE11. ### [`v4.2.0`](https://togithub.com/mohsinulhaq/react-popper-tooltip/releases/tag/v4.2.0): Revert to mouseenter/mouseleave hover mechanic [Compare Source](https://togithub.com/mohsinulhaq/react-popper-tooltip/compare/v4.1.2...v4.2.0) `v4.1.0` introduced a new way of handling hover trigger, which had a couple of improvements over the old one, but unintentionally led to another set of serious issues. We have now reverted to the older hover mechanic while also solving the older problems by setting `pointer-events: none` on the arrow as well as the non-interactive tooltip. ### [`v4.1.2`](https://togithub.com/mohsinulhaq/react-popper-tooltip/releases/tag/v4.1.2): Hover trigger bug fixes introduced in v4.1.0 🐛 [Compare Source](https://togithub.com/mohsinulhaq/react-popper-tooltip/compare/v4.1.1...v4.1.2) Fixes: [https://github.com/mohsinulhaq/react-popper-tooltip/issues/117](https://togithub.com/mohsinulhaq/react-popper-tooltip/issues/117) & [https://github.com/mohsinulhaq/react-popper-tooltip/issues/118](https://togithub.com/mohsinulhaq/react-popper-tooltip/issues/118) ### [`v4.1.1`](https://togithub.com/mohsinulhaq/react-popper-tooltip/compare/v4.1.0...v4.1.1) [Compare Source](https://togithub.com/mohsinulhaq/react-popper-tooltip/compare/v4.1.0...v4.1.1) ### [`v4.1.0`](https://togithub.com/mohsinulhaq/react-popper-tooltip/releases/tag/v4.1.0): An improved and more resilient hover trigger! Thanks to the contribution by [@&elastic#8203;czabaj](https://togithub.com/czabaj) 👑, the hover trigger is now improved quite a bit, accounting for the gap between the trigger and the tooltip and also fixing a glitch in cases where tooltip and trigger overlap. ### [`v4.0.0`](https://togithub.com/mohsinulhaq/react-popper-tooltip/releases/tag/v4.0.0): usePopperTooltip hook! 🪝 [Compare Source](https://togithub.com/mohsinulhaq/react-popper-tooltip/compare/v3.1.1...v4.0.0) ### Release notes With **react-popper**, used under the hood of **react-popper-tooltip**, introducing the `usePopper` hook in the last major update, we're now releasing the hook version of our own library as well - `usePopperTooltip`. The hook provides many new features and flexibility and allows for implementations not possible before. #### Breaking changes This release onwards, the hook is the only way of creating tooltips. This version drops the support of the `TooltipTrigger` render prop component. If you want to upgrade and still keep using render prop API, refer to our example section to implement the legacy API with our new hook. We wrote this version from scratch. Although thoroughly tested, it can still possibly contain some regressions. Please, report any problems using the [issues link](https://togithub.com/mohsinulhaq/react-popper-tooltip/issues). - For the sake of consistency, we made some changes to the props names. - `defaultTooltipShown` is renamed to `defaultVisible` - `tooltipShown` is renamed to `visible` - `onVisibilityChange` is renamed to `onVisibleChange` - `closeOnReferenceHidden` is renamed to `closeOnTriggerHidden` and the default value changed from `true` to `false` - The default placement is now `bottom` instead of `right`, in line with react-popper defaults. - The string value `"none"` for the prop `trigger` is replaced with `null`. - The default CSS has a few positioning and naming changes. - Previously, when a user hovered the tooltip, it stayed open to allow the user to interact with the tooltip's content. Now the tooltip closes as soon as the cursor leaves the trigger element. The new option `interactive` has been added to configure this behavior. - `getTriggerProps` and `arrowRef` are no longer needed. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyI6bWwiLCJUZWFtOk1MIiwiYmFja3BvcnQ6YWxsLW9wZW4iLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> (cherry picked from commit 71b34a9) # Conflicts: # package.json
This was referenced Jan 22, 2025
⏳ Build in-progress, with failures
Failed CI StepsHistory |
…t --include-path /api/status --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --update --no-serverless'
peteharverson
approved these changes
Jan 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport
This will backport the following commits from
mainto8.17: