docs: correct type name in editMenuItems client component example#15904
docs: correct type name in editMenuItems client component example#15904GermanJablo merged 2 commits intomainfrom
Conversation
…Props in edit-view.mdx Co-authored-by: GermanJablo <43938777+GermanJablo@users.noreply.github.com>
|
Pull Request titles must follow the Conventional Commits specification and have valid scopes. Unknown scope "docs" found in pull request title "fix(docs): correct type name in editMenuItems client component example". Scope must match one of: cpa, claude, db-*, db-d1-sqlite, db-mongodb, db-postgres, db-vercel-postgres, db-sqlite, db-d1-sqlite, drizzle, email-*, email-nodemailer, email-resend, eslint, graphql, kv, kv-redis, live-preview, live-preview-react, live-preview-vue, next, payload-cloud, plugin-cloud, plugin-cloud-storage, plugin-ecommerce, plugin-form-builder, plugin-import-export, plugin-mcp, plugin-multi-tenant, plugin-nested-docs, plugin-redirects, plugin-search, plugin-sentry, plugin-seo, plugin-stripe, richtext-*, richtext-lexical, richtext-slate, sdk, storage-*, storage-azure, storage-gcs, storage-r2, storage-uploadthing, storage-vercel-blob, storage-s3, translations, ui, templates, examples(/(\w|-)+)?, deps. |
|
🚀 This is included in version v3.79.1 |
The
editMenuItemsclient component example indocs/custom-components/edit-view.mdxreferenced a non-existent typeEditViewMenuItemClientProps. The correct exported type isEditMenuItemsClientProps.Changes
docs/custom-components/edit-view.mdx: ReplaceEditViewMenuItemClientProps→EditMenuItemsClientPropsin the client component code example (import and props type annotation)The server component example already correctly used
EditMenuItemsServerProps; the client example now follows the same naming pattern:Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.