-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
support for App\Models namespace #5
Comments
It's not how it works. I built the package with all my model in https://github.com/JhumanJ/laravel-model-stats/blob/main/src/Http/Controllers/HomeController.php#L29 |
Could be 2 issues here indeed. So Whereas |
I've just done a test where I have a model A extending a class B (itself extending model), and it worked just fine. Can you share details about your environment, and give more details about how to reproduce the issue? |
Did some more debugging. I think being able to specify the models directory, and only scan that models directory, is a better solution for big projects with a lot of deprecated code. In my case, getModels() fails on scanning some unused Console/Commands (with a broken dependency) and some other helper files (that aren't real classes with namespaces). |
I shall take a look at this. |
When looking into HomeController getModels(), I think the package is only scanning the App/ directory, and not App/Models.
Perhaps make this configurable?
The text was updated successfully, but these errors were encountered: