Releases: laravel-shift/blueprint
Releases · laravel-shift/blueprint
1.7.0
Added
json
validation rule
Fixed
- Pivot table and migration names
- Using HTTP
delete
method fordestroy
action. - PHP error for missing method during test generation
- Line ending issue with Windows
1.6.0
Another massive release as Blueprint received so many pull requests after the demo on Laracasts.
Highlights
- Set
password
andremember_token
inhidden
model attributes. - Use new
id()
column in migration for Laravel 7 applications. - Support for a
uuid
primary key shorthand in model definitions. - Separate
resource: api
code generation specifically for API actions. - Support for
belongsToMany
model relationships. - New
resource
statement to generate API Resource. - Automatic generation of pivot table migration when defining
belongsToMany
relationships. - Optionally generate DocBlock for model relationship methods for IDE resolution.
For a full list of the changes, you may review the diff between releases.
1.5.1
v1.5.1 Strengthen test with data provider
1.5.0
Lots of new features tagged in this release. I could argue making it 2.0, but technically there aren't any breaking changes. So here's 1.5.0!
Includes:
- New
blueprint:trace
command reads existing model definitions so you may reference them in draft files. This has all sorts of use cases like using Blueprint to generate code within existing projects or regenerating/consolidating previous migrations. (#69) - Support for defining additional
hasMany
andhasOne
model relationships (#72) - Improve support for defining models with
uuid
andjson
data types. (#76) - Fix
blueprint:erase
command properly clears previous file list (515e42) - New
respond
statement for sending HTTP status code responses or JSON payloads (e68501)
1.4.1
v1.4.1 fix: mismatched key casing (#70)
1.4.0
v1.4.0 Add support for Laravel 7 and PHPUnit 9
1.3.1
1.3.0
This release adds a new feature which will automatically generate the HTTP Tests for the defined controller actions in your draft file.
I expect a few bugs. So when you encounter them, please open an issue and include:
- Your draft file
- The incorrectly generated test code
- The expected test code
1.2.2
Generate faker data using precisions and scale for decimal
and float
columns in model factory.
1.2.1
v1.2.1 Strengthen factory generator tests