composer create-project laravel/laravel example-app
cd example-app
composer require -W --dev laravel-shift/blueprint
php artisan blueprint:new
# fill in draft.yaml as above
php artisan blueprint:build
As a workaround I can easily change the name of the column, but as-is the generated migration ends up with $table->enum('name', ["one","two","three"]);, so if nothing else, the logic seems to differ a bit between the Factory and Migration generators ¯\_(ツ)_/¯
Issue:
It's possible this is intended behavior, but feels more like a bug?
If I define a model with a column name of
name
and a typeenum
I would expect the generated factory definition to look like this
but instead I get
Looks like the
FactoryGenerator
looks for an implicit match before an explicit one: https://github.com/laravel-shift/blueprint/blob/4485f6b3491eaeca6c9d59114b5c1dd349f914d0/src/Generators/FactoryGenerator.php#L123Repro:
As a workaround I can easily change the name of the column, but as-is the generated migration ends up with
$table->enum('name', ["one","two","three"]);
, so if nothing else, the logic seems to differ a bit between the Factory and Migration generators ¯\_(ツ)_/¯