Trying to using exception lifecycle

[killallskywalker]

Currently just found out that in livewire have exception lifecycle hook . I try to use it , somehow it did't go through the exception function .

  in my component , on mount i trigger the ModelNotFoundException to see if the hook below  are triggered or not 

   public function exception($e, $stopPropagation) {
        if($e instanceof ModelNotFoundException) {
            dd('Not  execute');
        }
    }

Is there anything that i miss ? As per in doc it state -

The exception() hook allows you to do just that: you can perform check on the $error, and use the $stopPropagation parameter to catch the issue.

Thanks !

[lrljoe]

Make sure that you've got that exception available in your file

and call

$stopPropagation();

[marcusmoore]

I was able to throw a ModelNotFoundException from mount and catch it in the exception method but I did notice that it doesn't seem to work for exceptions thrown in computed properties.

[lrljoe]

Hmm

Catching it and passing it to the exception does work, so I suspect it's down to how Computed Properties are actually dealt with (via invading).

    #[Computed]
    public function somethingComputed()
    {
        // 2: uncomment the "throw new Exception" line and save the component (cmd+s).
        // Wirebox will reload the preview and this exception will render 
        // without landing in the exception() method.
        try {
            throw new Exception('from a computed property');    
        }
        catch (Exception $e)
        {
            $this->exception($e, true);
        }
        
        
        return 'I am text from a computed property';
    }

[marcusmoore]

Ah good thinking @lrljoe! 😄

[lrljoe]

Not a proper solution, but at least gives you a break-fix for now, will take a look at the exception capture for Computed attributes when I get a chance (unless someone else beats me to it), but hopefully you can at least progress for now!

For what it's worth, you could extend the Computed attribute, so that it exhibits that behaviour by default.

[lrljoe]

@marcusmoore - Just to note that this PR should help on the way to addressing this, as it starts to implement lifecycle hooks into the Form #8682

[marcusmoore]

@lrljoe Good thinking on extending the attribute. I might give that a try when I circle back to the work that this popped up in. I'll keep an eye on that PR as well.

Thanks for following up 😄