dualfroz 24cce423ab fix: distinguish PCRE failure from a mismatch in Assert::regex() ...

preg_match() has three outcomes -- 1, 0 and false -- but regex() folded
false into the "no match" branch. An uncompilable pattern or an exhausted
PCRE limit therefore leaked a raw PHP warning out of the library and then
reported the misleading "The value ... does not match the expected pattern."

Check for false separately and report the pattern together with
preg_last_error_msg(), following the existing false === $x = nativeCall()
handling in Assert::strlen(). The caller's custom message is intentionally
not reused for that branch, since it describes a mismatch that never
happened. Matching values and genuine mismatches are unaffected.

2026-09-06 00:59:17 +02:00

src

fix: distinguish PCRE failure from a mismatch in Assert::regex()

2026-09-06 00:59:17 +02:00

tests

fix: distinguish PCRE failure from a mismatch in Assert::regex()

2026-09-06 00:59:17 +02:00

S

Description

My contributions to webmozarts/assert: 2 commits

70 KiB

0 Stars 1 Watchers 0 Forks

Languages

PHP 100%