sidebar three level

Open
#1,191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
desktop, frontend

Research direction

The issue identifies only the sidebar menu and does not name a source file, control, or test. Start by locating the sidebar implementation and its existing two-level behavior; done means the supported nesting depth is expanded and the behavior is covered by a clear verification case.

Written by the indexing model from the issue text.

Description

bug
Describe the bug

So far, the sidebar menu only supports two levels. We hope to support unlimited levels, or at least three to four levels.

To Reproduce

So far, the sidebar menu only supports two levels. We hope to support unlimited levels, or at least three to four levels.

Expected behavior

So far, the sidebar menu only supports two levels. We hope to support unlimited levels, or at least three to four levels.

Screenshots

So far, the sidebar menu only supports two levels. We hope to support unlimited levels, or at least three to four levels.

OS version

So far, the sidebar menu only supports two levels. We hope to support unlimited levels, or at least three to four levels.

.NET version

So far, the sidebar menu only supports two levels. We hope to support unlimited levels, or at least three to four levels.

WPF-UI NuGet version

So far, the sidebar menu only supports two levels. We hope to support unlimited levels, or at least three to four levels.

Additional context

So far, the sidebar menu only supports two levels. We hope to support unlimited levels, or at least three to four levels.

Dominant language
C#
Stars
9.6k
Forks
1k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lepoco/wpfui

All issues in lepoco/wpfui

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.