Repository navigation
FILTER_THROW_ON_FAILURE flag? #16710
Description
Description
a FILTER_THROW_ON_FAILURE alternative to the existing FILTER_NULL_ON_FAILURE would be nice. Could behave pretty much like the existing JSON_THROW_ON_ERROR
usage scenario: replace code like
$b = filter_var($v1, FILTER_VALIDATE_BOOL, FILTER_NULL_ON_FAILURE);
if($b === null) {
throw new ValueError("failed FILTER_VALIDATE_BOOL");
}
$i = filter_var($v2, FILTER_VALIDATE_INT);
if($i === false) {
throw new ValueError("failed FILTER_VALIDATE_INT");
}with
$b = filter_var($v1, FILTER_VALIDATE_BOOL, FILTER_THROW_ON_FAILURE);
$i = filter_var($v2, FILTER_VALIDATE_INT, FILTER_THROW_ON_FAILURE);
Activity
cmb69 commentedon Nov 6, 2024
Makes sense, but we need to consider the behavior of
filter_var_array().iluuu1994 commentedon Nov 6, 2024
This has some overlap with pattern matching, more specifically the
askeyword. It's not a full alternative, given that pattern matching doesn't support e-mails, URLs, etc.DanielEScherzer commentedon Mar 25, 2025
I'd say that any time FILTER_NULL_ON_FAILURE would trigger returning null, we would throw, to be consistent
This probably needs an RFC the same way that https://wiki.php.net/rfc/json_throw_on_error did, I'll add this to my list but I already have two RFCs under discussion at the moment
DanielEScherzer commentedon Jun 21, 2025
@divinity76 I've created a PR for this, can you help provide an example use case that I can put in the RFC?