Resolving DB Factory Namespace Issue on Laravel 8.x #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In this PR, we are resolving #39, where we are creating the model factory class within subdirectories and updating the class namespace.
How to test on localhost
$ laravel new simple_crud_test
$ cd simple_crud_test
phpunit.xml
using sqlite in memory database$ composer require laravel/ui
$ composer require luthfi/simple-crud-generator dev-39_db_factory_namespace_issue --dev
$ php artisan ui bootstrap --auth
$ php artisan make:crud Phone
(Phone
model on theapp/Models
directory)$ vendor/bin/phpunit
(all tests are passed)$ php artisan make:crud Entities/Units/Unit
(Unit
model on theapp/Entities/Units/Unit
directory)$ vendor/bin/phpunit --stop-on-failure
UnitFactory
on thedatabase/factories/Entities/Units
directory).Screenshot