Should I make an exception for user input errors?

Question

I am writing a user input library to easily manage the dynamic creation of forms to query users for data.

I wanted the end developer to "think" about the minimum minimum, so I went to exclude them instead of returning "true" or "false" and remember that we need to process the return value, etc.

In fact, everything turned out very well. Throwing exceptions also gave me the advantage that you can automatically log user errors in the log, all for “free” ones, since throwing an exception causes the logging to be performed.

Having said all this, I was wondering if this is really “against best practices”? Should I save exceptions only in those moments when I did not even expect a user input error, or is it okay to say: "the user has a problem ... what is the exception"?

Any thoughts?

Answer 1

Exceptions for exceptional cases.

Bad user input is the expected case, and (in my opinion) you should always try to validate and massage it in the correct format before displaying an error message that is not exceptional.

Answer 2

Symfony Form Validator throws exceptions.

, , , , , , .

Answer 3

. - .

( Java): Errors. . . , Errors, , , , .

Answer 4

In my personal opinion, this is due to where you are going to deal with the error. If it fills the code tree enough, Exeption will be reasonable. If you just catch it 3 lines below, it is a waste of resources (it contains full backtracking), and inline error handling will be fine, for which you can easily add (the same) logging capability.