Skip to content

Commit

Permalink
Release 0.8.0
Browse files Browse the repository at this point in the history
  • Loading branch information
JasperTey committed Nov 13, 2023
1 parent 007e3e8 commit acee977
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,16 @@

All notable changes to `laravel-ddd` will be documented in this file.

## [Unversioned]
## [0.8.0] - 2023-11-12
### Changed
- Implement more robust handling of base models when generating a domain model with `ddd:model`:
- Implement proper support for custom base models when when using `ddd:model`:
- If the configured `ddd.base_model` exists (evaluated using `class_exists`), base model generation is skipped.
- If `ddd.base_model` does not exist and falls under a domain namespace, base model will be generated.
- Falling under a domain namespace means `Domain\**\Models\SomeBaseModel`.
- For example, if `ddd.base_model` were set to `App\Models\CustomAppBaseModel` or `Illuminate\Database\Eloquent\NonExistentModel`, they fall outside of the domain namespace and won't be generated on your behalf.
- Falling under a domain namespace means `Domain\**\Models\**`.
- If `ddd.base_model` were set to `App\Models\NonExistentModel` or `Illuminate\Database\Eloquent\NonExistentModel`, they fall outside of the domain namespace and will not be generated for you.

### Fixed
- Resolve long-standing issue where `ddd:model` would not properly detect whether the configured `ddd.base_model` already exists, leading to unpredictable results when `ddd.base_model` deviated from the default `Domain\Shared\Models\BaseModel`.
- Resolve long-standing issue where `ddd:model` would not properly detect whether the configured `ddd.base_model` already exists, leading to unintended results.

### Chore
- Update composer dependencies.
Expand Down

0 comments on commit acee977

Please sign in to comment.