How about throw exceptions? about laravel-best-practices HOT 5 OPEN

@alexeymezenin

from laravel-best-practices.

@AliverdiSultanli I'm sorry, I don't understand the question.

from laravel-best-practices.

@alexeymezenin How we can write code about throw exception with best practice? With try catch or another style?

from laravel-best-practices.

Laravel automatically converts some types of exceptions to appropriate HTTP errors which is great because we don't need to handle those. With other types of exceptions just use standard try/catch.

from laravel-best-practices.

There few things which can improve your code while dealing with exceptions.

1. Always throw specific exceptions, rather than generic Exceptions, and if it's related to HTTP, add status code as well.
2. Though application-specific exceptions can easily be caught by the simple catch statement with that specific exception type, however, if you dealing with some data dependent on an external source, you might want to also catch Throwable, this will allow you to capture exception like missing array index, and help you to log later the exception to an external system like sentry.
3. Use finally, with try catch statement, it will help you to execute some cleanup stuff.

from laravel-best-practices.