8000 Correctly detect max depth of NestedSelect if level is empty by philippjfr · Pull Request #7194 · holoviz/panel · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@philippjfr
Copy link
Member

Empty levels were not treated correctly, resulting in errors when a leaf was empty and incorrectly treating a two-level NestedSelect as a single level

@philippjfr philippjfr added this to the v1.5.0 milestone Aug 27, 2024
@codecov
Copy link
codecov bot commented Aug 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.23%. Comparing base (4907011) to head (26a00e0).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7194      +/-   ##
==========================================
- Coverage   82.23%   82.23%   -0.01%     
==========================================
  Files         331      331              
  Lines       49359    49360       +1     
==========================================
- Hits        40591    40589       -2     
- Misses       8768     8771       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@philippjfr philippjfr merged commit d0976d8 into main Aug 27, 2024
@philippjfr philippjfr deleted the nested_select_fix branch August 27, 2024 14:28
assert select._widgets[0].value == 'Ben'
assert select._widgets[0].visible
assert select.value == {0: 'Ben'}
assert select.value == {0: 'Ben', 1: None}
Copy link
Contributor
@ahuang11 ahuang11 Aug 29, 2024

Choose a reason for hiding this comment

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

I'm wondering if this 1: None is correct?

Copy link
Member Author

Choose a reason for hiding this comment

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

Seems correct to me, there are two levels after all, even if one of them is empty.

@github-actions
Copy link
github-actions bot commented Sep 9, 2025

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0