Skip to content
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

Default app_path in setting is not same after built model #21

Open
gtokung opened this issue Feb 22, 2017 · 4 comments
Open

Default app_path in setting is not same after built model #21

gtokung opened this issue Feb 22, 2017 · 4 comments

Comments

@gtokung
Copy link

gtokung commented Feb 22, 2017

Laravel 5.4 with propelLaravel last version
before built :
in configuration the default path is 'phpDir' => app_path('Models'),

but after i built the model it generate file and write namespace like this-> namespace App\Modules;
it's bug that i found.

pls solved this issue or tell me how to fixed

Thank you.

@SCIF
Copy link
Contributor

SCIF commented Feb 22, 2017

@gtokung , write down path for newely generated model related to root of your application, please. Models obviously uses namespaces so I don't understand what's your concern. Provide actual and expected state and I will can help you.

@gtokung
Copy link
Author

gtokung commented Feb 22, 2017

OK. the problem is when i set config phpDir in config/propel.php like this ('phpDir' => app_path('Models'))
and then i build with command => php artisan propel:model:build
it's generate new folder "Models" but the file inside this folder like Users.php it's use namespace like => "namespace App\Modules;"

it should be "namespace App\Models;", Right?

Thank you.

@SCIF
Copy link
Contributor

SCIF commented Feb 22, 2017

@gtokung , actually namespace should be specified in schema.xml: http://propelorm.org/documentation/reference/schema.html#database-element If you are running initial installation, then init command will try to detect your basic namespace from composer.json file.

@gtokung
Copy link
Author

gtokung commented Feb 23, 2017

Thank You.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants