Using Moonshine in a multi-module context #1926
Unanswered
stevebrainng
asked this question in
Q&A
Replies: 1 comment 8 replies
-
|
@lee-to I hope you can see why I was talking about Namespaces in my previous discussion ? |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, so I finally installed and replaced Filament with Moonshine in the Cms we're building.
My first issue is that I want to be able to use the Moonshine in different modules and plugins.
So currently we installed Moonshine in packages/panel and the PanelProvider register class has this :
This looks great so far, but when creating a page or resources in individual plugins or modules I expect the "php artisan moonshine:page" create commands to load all the registered namespaces directories. but it's not posible to add more than one (the primary) directory to the config.
In Filament you can just register a custom namespace and filament will load pages and resources from those directories.
the only way to load pages and resources is manually creating a page and then adding it to the pages or resourcce array below, which is not very efficient for our use case.
Anyway on how to handle this better?
Also not all the configurable moonshine.php configs are available programmatically.
Beta Was this translation helpful? Give feedback.
All reactions