Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
c-tanner authored Sep 29, 2024
1 parent 6594333 commit 1f18789
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,13 @@ Requirements:

`composer require c-tanner/laravel-deep-sync`

## Beyond cascading soft deletes
## More than just cascading soft-deletes

Cascading soft-deletes within Laravel has been covered by a number of great packages in the past. At it's core, though, `deleted_at` is just another class property.
Cascading soft-deletes within Laravel has been covered by a number of great packages in the past. At its core, though, `deleted_at` is just another class property.

With DeepSync, you can assign any model property as `syncable` - and choose which models should follow suit:
While DeepSync does offer native support for cascading / syncing soft-deletes, you can also assign _any_ model property as `syncable` - and choose which models should follow suit.

Let's take the classic `User` / `Post` example:

```php
#[ObservedBy([DeepSync::class])]
Expand Down

0 comments on commit 1f18789

Please sign in to comment.