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

Feature Request: Allow Child Content in RadzenProfileMenuItem Component #1754

Open
mikemassa84 opened this issue Oct 25, 2024 · 0 comments
Open

Comments

@mikemassa84
Copy link

Is your feature request related to a problem? Please describe.
RadzenProfileMenuItem does not allow embedding components.

Describe the solution you'd like
It would be useful to allow RadzenProfileMenuItem to accept child content similar to the RadzenPanelMenuItem. This would allow us to add switches and other components to the profile menu. One example use case of this could be including a RadzenSwitch or the RadzenAppearanceToggle to allow theme switching directly from a profile menu option.

Describe alternatives you've considered
I've gotten around this by adding the Click listener to the RadzenProfileMenu and executing a theme switch (toggle between light/dark) in the click handler method. This works but the profile menu item is displayed as Text and Icon only and it might be a nicer look to have one of the more complex components available in place of the text.

Additional context
I would like to do something like this:

<RadzenProfileMenu>
    <Template>
        <RadzenGravatar Email="[email protected]">
         </RadzenGravatar>
    </Template>
    <ChildContent>
        <RadzenProfileMenuItem>
            <RadzenSwitch Change=@(args => OnChange(args, "Switch")) />
        </RadzenProfileMenuItem>
        <RadzenProfileMenuItem Text="Buttons" Path="buttons" Icon="account_circle"></RadzenProfileMenuItem>
    </ChildContent>
</RadzenProfileMenu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant