Filter should use exceptions

[mbrevda]

Validating code ends up requiring lots of if statements. Filter should be callable without worrying about its response, with exceptions throw to halt execution, when necessary.

for example:
Boilerplate:

$this->filter(...);
$data = ['foo' => 'bar'];

Before:

$success = $filter->values($data);
if (! $success) {
    $messages = $filter->getMessages();
    // do something with $messages;
}

After:

// exceptions can be caught anywhere in the stack
$filter->values($data);

[harikt]

I don't think so.

[pmjones]

Wish granted! See the new develop-2 work, via __invoke(), where a FilterFailed exception is thrown.

[mbrevda]

So now filters can be called either as invokables or with ->getValues(), correct? (In my current stack, I specifically DONT want an exception thrown...)

[pmjones]

Or as ->values(), yes. Only __invoke() will throw the exception.

[mbrevda]

perfect

On Mon Dec 29 2014 at 3:45:38 PM Paul M. Jones notifications@github.com
wrote:

Or as ->values(), yes. Only __invoke() will throw the exception.

—
Reply to this email directly or view it on GitHub
#34 (comment).