You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
In an application architecture where one opted to move their application codes outside of the Framework (Laravel) they could probably house their Entities/metadata in a specific directory outside of Laravel's "app/" directory. In that case the metadata will not resolve correctly even if you set the correct namespace in doctrine.php config file since the ServiceProvider is looking for Laravel's default path app_path(). Could you support that and then probably add an optional "path" (in addition to namespace) in the doctrine.php config file? So that it's looking for the desired location?
The text was updated successfully, but these errors were encountered:
In an application architecture where one opted to move their application codes outside of the Framework (Laravel) they could probably house their Entities/metadata in a specific directory outside of Laravel's "app/" directory. In that case the metadata will not resolve correctly even if you set the correct namespace in doctrine.php config file since the ServiceProvider is looking for Laravel's default path app_path(). Could you support that and then probably add an optional "path" (in addition to namespace) in the doctrine.php config file? So that it's looking for the desired location?
The text was updated successfully, but these errors were encountered: