starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-07-08 18:16:08 +00:00
Code Issues 1.3k Packages Projects Releases 28 Wiki Activity

[PR #1214] [CLOSED] Create context menu separators without RenderFragment #2600

New Issue
Open
opened 2026-01-29 18:19:35 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 18:19:35 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/radzenhq/radzen-blazor/pull/1214
Author: @gauss-lvs-dev
Created: 10/23/2023
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (2)

  • ef82623 Added ContextMenuSeparator in order to create separator programmatically
  • ac9209e Merge branch 'radzenhq:master' into master

📊 Changes

2 files changed (+10 additions, -1 deletions)

View changed files

📝 Radzen.Blazor/ContextMenuService.cs (+5 -0)
📝 Radzen.Blazor/RadzenContextMenu.razor (+5 -1)

📄 Description

I created a ContextMenuSeparator class that extends ContextMenuItem and modified RadzenContextMenu to distinguish between those to types. I feels a litte bit more "natural" to me than the following approaches.

Another approach would be to create a simple "IsSeparator" property which RadzenContextMenu checks against. Yet another approach could be to create the properties "InsertSeparatorAfter" or "InsertSeparatorBefore".

I am happy to contribute any approach, if you want me to.

Someone created an issue 5 days ago (#1201)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/radzenhq/radzen-blazor/pull/1214 **Author:** [@gauss-lvs-dev](https://github.com/gauss-lvs-dev) **Created:** 10/23/2023 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (2) - [`ef82623`](https://github.com/radzenhq/radzen-blazor/commit/ef82623eb19cc75ead140762b9dfc56969546803) Added ContextMenuSeparator in order to create separator programmatically - [`ac9209e`](https://github.com/radzenhq/radzen-blazor/commit/ac9209ee8bad604628a8661077eae8bf6713504c) Merge branch 'radzenhq:master' into master ### 📊 Changes **2 files changed** (+10 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `Radzen.Blazor/ContextMenuService.cs` (+5 -0) 📝 `Radzen.Blazor/RadzenContextMenu.razor` (+5 -1) </details> ### 📄 Description I created a ContextMenuSeparator class that extends ContextMenuItem and modified RadzenContextMenu to distinguish between those to types. I feels a litte bit more "natural" to me than the following approaches. Another approach would be to create a simple "IsSeparator" property which RadzenContextMenu checks against. Yet another approach could be to create the properties "InsertSeparatorAfter" or "InsertSeparatorBefore". I am happy to contribute any approach, if you want me to. Someone created an issue 5 days ago (#1201) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-29 18:19:35 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#2600
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?