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
Multiple namespaces #22
Comments
Found it: |
Hi @Surt ! Yeah, I could take this with me in the next release. Just to be clear: do you just want the path to be configurable pointing to another f.e. |
Array of paths please, so it mimics composer's autoload PSR-4 mapping. I suffer the same issue as OP, that it's only loading in models in the App\ namespace even if I change the model-namespace configuration. - which makes for a rather empty schematic on our setup 😢 (otherwise, this is a pretty freaking awesome package! kudos) |
Thanks @SlyDave! Working on the array of paths, coming soon! |
Works great! - Thanks :)
(obviously replace "MyModels" with your models directory; don't call your models folder MyModels ;P) |
Yeah! Works great! Thank you! |
Hello,
eager to try the package.
Actually I have multiple namespaces and can't make
schematics
to read them. I need to set the config for each individual package. Since some packages make use of others I can't make them appear on the interface.Can I trick
schematics
to scaffold a "base" namespace, so it finds the "models" in there?Edited: The config only affects new models forms etc... the scaffolding is not working right now.
I'm using https://github.com/nWidart/laravel-modules, nothing fancy, just a way to divide the code into components, 100% laravel way. But still...
The text was updated successfully, but these errors were encountered: