-
Notifications
You must be signed in to change notification settings - Fork 74
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
remove state-sync for data menu open #2670
remove state-sync for data menu open #2670
Conversation
8ccd8fb
to
f276ed6
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2670 +/- ##
=======================================
Coverage 91.52% 91.53%
=======================================
Files 161 161
Lines 20196 20196
=======================================
+ Hits 18485 18486 +1
+ Misses 1711 1710 -1 ☔ View full report in Codecov by Sentry. |
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.
p.s. I rebased this PR on top of |
I cannot imagine how that would possibly be related to this, but if you can consistently reproduce here but not on main, I can investigate. |
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.
If that tool swapping thing is unrelated, then your patch also fixed the original problem.
I guess it is up to POs to see what users would prefer? Thanks!
This was discussed today and the decision was to move forward with review on this PR, and if it doesn't show any major drawbacks, go with this approach since it's a less-significant behavior change. |
Co-authored-by: Kyle Conroy <[email protected]>
Description
As an alternate option to #2669, this decouples each data-menu from other instances in the same viewer (so only a single menu will be open if multiple instance of the app are being shown).
Fixes #2581
Close #2669
Change log entry
CHANGES.rst
? If you want to avoid merge conflicts,list the proposed change log here for review and add to
CHANGES.rst
before merge. If no, maintainershould add a
no-changelog-entry-needed
label.Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
trivial
label.