-
Notifications
You must be signed in to change notification settings - Fork 3k
feat(next): export views, pass all props to custom dashboard view #14094
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
Conversation
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
🚀 This is included in version v3.59.0 |
Amazing feature, @AlessioGr! I suggested #13936 and #13935 to help me customize DashboardView because recreate everything is kind of sad haha I guess I'll be able to reuse DashboardView Is there any documentation? import { AccountView } from "@payloadcms/next/views";
import { AdminViewServerProps } from "payload";
const AccountViewPage = async(props: AdminViewServerProps) => {
return (
<AccountView {...props} />
)
}
export default AccountViewPage; ![]() |
@payloadcms/next
likeDashboardView
, which are useful for when you provide your own view but want to render parts of the default viewreq
select
API inpayload.find
call of the dashboard view for improved performance