guidocella/eloquent-populator 问题修复 & 功能扩展

解决BUG、新增功能、兼容多环境部署,快速响应你的开发需求

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

guidocella/eloquent-populator

Composer 安装命令:

composer require guidocella/eloquent-populator

包简介

Guess attributes for Eloquent model factories

README 文档

README

This package provides default attributes for Laravel model factories by guessing the best Faker formatters from columns' names and types. For example, if a column is called first_name, it will use $faker->firstName(). If unable to guess by the column's name, it will guess the formatter by the column's type; for example, it will use $faker->text() for a VARCHAR column, or a Carbon instance for a TIMESTAMP. Models of BelongsTo relationships that have been defined are created as well. Furthermore, if you use the Multilingual package, for translatable attributes Populator will generate arrays with a different value for each configured locale.

Compared to packages that generate factories once, you generally don't have to update your factories as you change their table definitions and they will be very small.

Installation

Install the package with Composer:

composer require --dev guidocella/eloquent-populator

Model factory integration

Call Populator::guessFormatters($this->modelName()) in your factories' definition methods to get an array with the guessed formatters. You may merge these with custom attributes whose guessed formatter isn't accurate.

use GuidoCella\EloquentPopulator\Populator;

...

public function definition(): array
{
    return [...Populator::guessFormatters($this->modelName()), ...[
        'avatar' => $this->faker->imageUrl()
    ]];
}

If you execute php artisan stub:publish, you can include the call to Populator in factory.stub so that php artisan make:factory will add it.

After guessing a model's formatters once, they are cached in a static property even across different tests.

Seeding

Before seeding your database you'll want to call setSeeding().

public function run()
{
    Populator::setSeeding();

Its effect is that nullable columns will have a 50% chance of being set to null or to the guessed formatter.

Testing

If setSeeding() wasn't called nullable columns will always be set to their guessed formatter. The idea is to simplify tests such as this:

public function testSubmitWithoutName() {
    $user = User::factory()->make(['name' => null]);
    // test that submitting a form with $user's attributes causes an error
}

public function testSubmitWithCorrectName() {
    $user = User::factory()->make();
    // no need to specify the correct formatter for name since it can't be null
    // test that submitting a form with $user's attributes is succesful
}

On the other hand, seeding the database with null attributes lets you notice Trying to get property of non-object errors.

统计信息

  • 总下载量: 62.63k
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 77
  • 点击次数: 0
  • 依赖项目数: 2
  • 推荐数: 0

GitHub 信息

  • Stars: 76
  • Watchers: 5
  • Forks: 9
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2016-12-16

承接程序开发

PHP开发

VUE

Vue开发

前端开发

小程序开发

公众号开发

系统定制

数据库设计

云部署

网站建设

安全加固