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

Fix retention for data summary collapses triggered by splitter button and resizing #6520

Closed
wants to merge 2 commits into from

Conversation

kv9898
Copy link
Contributor

@kv9898 kv9898 commented Feb 27, 2025

Release Notes

New Features

  • N/A

Bug Fixes

After this fix, it is also safe to close #5572 .

demonstration1.mp4

QA Notes

  • NA

Copy link
Contributor

@samclark2015 samclark2015 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR! I tested locally and have a couple comments.

Comment on lines +344 to +348
if (collapsed) {
context.instance.collapseSummary();
} else {
context.instance.expandSummary();
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This works after the first attempt. From a fresh Positron start, collapsing it, switching away & back, and returning does not hold state. See video below:

Screen.Recording.2025-02-27.at.10.55.07.AM.mov

I will explore more this afternoon. Do you see this behavior as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weird... No, it works for me on the first attempt. Does this problem still arise after you restart the Positron development version?

Copy link
Contributor

@samclark2015 samclark2015 Feb 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's still not right for me, but @softwarenerd was able to confirm that it works as expected... so likely something in my working copy.

@kv9898
Copy link
Contributor Author

kv9898 commented Feb 27, 2025

Feel free to edit my code!

Copy link
Contributor

@samclark2015 samclark2015 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All looks good!

Comment on lines +344 to +348
if (collapsed) {
context.instance.collapseSummary();
} else {
context.instance.expandSummary();
}
Copy link
Contributor

@samclark2015 samclark2015 Feb 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's still not right for me, but @softwarenerd was able to confirm that it works as expected... so likely something in my working copy.

Copy link
Contributor

@softwarenerd softwarenerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This appears to be working for me. Thanks for the PR!

@kv9898
Copy link
Contributor Author

kv9898 commented Feb 28, 2025

@softwarenerd @samclark2015 I do not need to worry about the failed tests or merging, right? Anything else that needs to be done on my part?

@samclark2015
Copy link
Contributor

Correct, we will merge in today. Thanks again for this!

@samclark2015
Copy link
Contributor

Merged in #6550 (duplicate of this PR to allow tests to run).

@github-actions github-actions bot locked and limited conversation to collaborators Feb 28, 2025
@kv9898 kv9898 deleted the fix-button-retention branch February 28, 2025 15:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants