fix(livechat): type Menu ref and remove legacy base usage#40126
fix(livechat): type Menu ref and remove legacy base usage#40126probeen007 wants to merge 3 commits intoRocketChat:developfrom
Conversation
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
WalkthroughThe Menu component in LiveChat was refactored to improve type safety by replacing the untyped Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hi maintainers, this PR is ready from my side. label: stat: QA assured |
|
Tip For best results, initiate chat on the files or code changes.
Here are a few suggestions to get their attention:
The code changes in this PR look well-scoped and the pre-merge checks are all passing — hopefully a maintainer can take a look and set the required metadata soon! 🙌 🧠 Learnings used |
|
Hi @julio-rocketchat , this PR is ready from my side. Could you please add: label: stat: QA assured |
|
Proposed changes
Fix LiveChat
Menuref typing to use the actual DOM element contract instead ofany.PopoverMenuWrappernow stores aHTMLDivElement | nullref and reads bounds directly from the element withgetBoundingClientRect(), removing the legacy.basecomponent-instance dependency.Issue(s)
Closes #39128
Steps to test or reproduce
Further comments
This change is intentionally scoped to the ref-typing issue reported in #39128. It improves type safety without changing runtime behavior.
Summary by CodeRabbit