Skip to content

Commit 15a8d5d

Browse files
[skip ci] update readme
1 parent 2a4460d commit 15a8d5d

File tree

1 file changed

+1
-15
lines changed

1 file changed

+1
-15
lines changed

README.md

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Cascading soft deletes for the Laravel PHP Framework
2-
## v1.4.0
2+
## v2.0.0
33

44
![Travis Build Status](https://travis-ci.org/michaeldyrynda/laravel-cascade-soft-deletes.svg?branch=master)
55
[![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/michaeldyrynda/laravel-cascade-soft-deletes/badges/quality-score.png?b=master)](https://scrutinizer-ci.com/g/michaeldyrynda/laravel-cascade-soft-deletes/?branch=master)
@@ -18,20 +18,6 @@ It may be useful to be able to restore a parent record after it was deleted. In
1818

1919
In doing so, however, you lose the ability to use the cascading delete functionality that your database would otherwise provide. That is where this package aims to bridge the gap in functionality when using the `SoftDeletes` trait.
2020

21-
As of `v1.0.2`, you can inherit `CascadeSoftDeletes` from a base model class, you no longer need to use the trait on each child if all of your models happen to implement `SoftDeletes`.
22-
23-
As of `v1.0.4`, the package supports cascading deletes of grandchildren records ([#8](https://github.com/michaeldyrynda/laravel-cascade-soft-deletes/issues/8), [#9](https://github.com/michaeldyrynda/laravel-cascade-soft-deletes/pull/9)).
24-
25-
As of `v1.0.5`, the package has better support of `hasOne` relationships ([#10](https://github.com/michaeldyrynda/laravel-cascade-soft-deletes/issues/10), [#11](https://github.com/michaeldyrynda/laravel-cascade-soft-deletes/issues/11)).
26-
27-
`v1.1.0` adds compatibility with Laravel 5.3.
28-
29-
`v1.2.0` adds compatibility with Laravel 5.4.
30-
31-
`v1.3.0` adds compatibility with Laravel 5.5.
32-
33-
`v1.4.0` adds compatibility with Laravel 5.6.
34-
3521
## Code Samples
3622

3723
```php

0 commit comments

Comments
 (0)