Navigation Makes More Sense on as a DashboardLayout prop

[aress31]

Summary

Applying the navigation prop directly to the DashboardLayout component is logical, as it governs the drawer items and navigation. This approach enables the creation of multiple DashboardLayouts, each with its unique set of navigation items.

Examples

No response

Motivation

Separating the AppProvider from the DashboardLayout in terms of navigation.

Search keywords: navigation

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

@aress31 How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.

[Janpot]

Navigation Makes More Sense on as a DashboardLayout prop

counter argument: both dashboard layout and page header components need to look at the same navigation structure to provide a coherent experience between them. Your use case of multiple layouts rendered together seems a very theoretical one to me. do you have any real world use cases for this?