Currently, when an ArithmeticException is thrown when resolving expression, we are adding a TemplateError with ErrorReason.EXCEPTION to the interpreter.
Since ArithmeticException is caused by users' input errors, this PR changes to add a TemplateError with ErrorReason.INVALID_INPUT when ArithmeticException is caught.
Currently, when an
ArithmeticException
is thrown when resolving expression, we are adding aTemplateError
withErrorReason.EXCEPTION
to the interpreter.Since
ArithmeticException
is caused by users' input errors, this PR changes to add aTemplateError
withErrorReason.INVALID_INPUT
whenArithmeticException
is caught.