Skip to content

atnd5 Menu component - add support for default selected keys #128

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

Closed
wants to merge 1 commit into from

Conversation

CallumBoase
Copy link
Contributor

CONTEXT

The Antd Menu component is well-suited for building the navigation menu for a website or app being created in Plasmic studio.

Of course, when building a website navigation bar, it's important to show the user what page they are currently on
image

The default selected keys prop of the antd menu component allows specification of the default (initially selected) menu items.

PROBLEM

The existing Plasmic code component registratoin for antd5 Menu component does not allow the user to specify the default selected keys prop of the Antd Menu component.

SOLUTION
This PR adds support for the missing prop.

This allows Plasmic studio users to flexibly control which menu item/s are selected when the component first loads.

In the context of creating an app/website navigation menu, here is an example of how this new prop can be used effectively:

2024-08-16.15-24-30.-.Menu.default.selected.key.option.mp4

Copy link

vercel bot commented Aug 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
plasmic-cms-i18n ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 16, 2024 5:30am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
react-email-demo ⬜️ Ignored (Inspect) Aug 16, 2024 5:30am

@sarahsga
Copy link
Contributor

The commit has been merged:
fd803bd

@sarahsga sarahsga closed this Aug 21, 2024
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

Successfully merging this pull request may close these issues.

2 participants