Skip to content

Commit 1038dac

Browse files
committed
chore: changeset for the sidebar area election
Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L9qibz6e1jru1WvD8e9e9E
1 parent 1d6bc8f commit 1038dac

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
'@object-ui/app-shell': patch
3+
---
4+
5+
fix(console): the sidebar opens on the area that holds the current page
6+
7+
Clause-②: no
8+
Metadata-protocol: none
9+
10+
In an app with several `areas`, the Console sidebar always opened on the first visible area, so a deep link, a bookmark or a per-audience `landing` that named an entry of a later area showed a menu that did not contain the page the reader was on. Now, on the first render and whenever the route moves to a page no entry of the shown area addresses, the sidebar shows the area whose navigation holds the entry the route addresses, and that entry is highlighted. The match is the one that already highlights the active row, so the area and the highlight agree. With no area holding such an entry, the sidebar keeps the area it shows, else the first visible one. A reader's own area pick holds while they stay on a page an entry of that area addresses.

0 commit comments

Comments
 (0)