Eloquent collection gets null in-place of a deleted model on $collection->fresh()

[aleedhillon]

• Laravel Version: 7.8.1
• PHP Version: 7.4.4
• Database Driver & Version: MySQL v5.7.29

Description:

When we delete an model from an Eloquent collection like so

$collection->find($id)->delete()

or just

Model::find($id)->delete()

and then to get the latest data use

$collection = $collection->fresh()

it return null in the place of deleted model. And then if you send this collection to your view you will obviously get error trying to get property of null.
So shouldn't fresh() method just remove that deleted model from the collection instead of placing a null in it's place or this is the intended behavior and we should instead do

$collection = Model::all()

to get the latest data after a delete.

Steps To Reproduce:

Fetch an Eloquent collection of any model from database and then delete any model that is in that collection and then use the $collection->fresh() method to get the fresh data from database.

[dwightwatson]

That's the behaviour if you called fresh() on a single record that has since been deleted (i.e. it returns null, so I would sort of expect the same if you called it on a collection. I think forcing you to call fresh()->filter() is better as it is much more explicit about your intention.

[driesvints]

Hey there,

Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

• Laracasts Forums
• Laravel.io Forums
• StackOverflow
• Discord
• Larachat
• IRC

Thanks!