Fix reset() to ensure a property initially set to null can be reset

[Simoneu01]

Failing test for #6540

When the reset() method is called on a property with default null will destroy the property from the component.
Livewire\Exceptions\PropertyNotFoundException : Property [$nullProp] not found on component:

With Livewire V2 instead when the reset() method was called it would reset the property to null

[edalzell]

Likely caused by #6345 and/or #6375

[joshhanley]

@Simoneu01 thanks for the PR!

I've fixed the issue and made sure that the FormObject's reset test also passes (as per PR #6375 thanks to @markjaquith).

Hope this helps!

[levu42]

@joshhanley shouldn't it be afterFirst & beforeFirst? When I unset a.b.c, then it's $component->a that should be unset, not $component->{'a.b'}, no?

[joshhanley]

@levu42 Hmm not sure I exactly follow the abc example, but if you have a form object that has a $foo property that should be unset, then first you need to get $component->form and then unset $foo on the form object.

[levu42]

@joshhanley When a form has an array, let's say $component->postForm has a user property as an array with user.name

class PostForm {
    public array $user = [
        'name' => 'Foo',
        'email' => null,
    ];
}   

And then in the component you do $this->reset('postForm.user.email'), then the split should be postForm & user.email. With your code of afterLast & beforeLast, it would be split into postForm.user & email, no?

I know it's a super narrow edge case, and not sure, if it's possible at all, but I thought about it reading the code and wanted to just make sure there's not a new bug introduced quietly with this fix that then takes ages to debug in the future :)

[joshhanley]

@levu42 Yep that's how I intended it to be split, because I need to see if email is already unset or not on portForm.user. Hence I use after last as the end property I need is email. The data_get handles the postForm.user part. Does that makes sense?

Ps sorry about poor formatting, on mobile 😬

[levu42]

@joshhanley that makes sense! Thanks for explaining :)

[calebporzio]

Lovely, thanks!