[sk4rp]

• Added or updated tests
• Documented user facing changes

Changes

CacheKeyAndTagsGenerator::key() joined argument values with implode(), which stringifies false and null to '' and true to '1'.
As a result, foo(flag: false) and foo(flag: null) shared one cache entry, so @cache could return the result of a different argument value.

All non-object argument values are now JSON encoded, so each value keeps its type in the key: arg:null, arg:false, arg:true, arg:"null", arg:5, arg:[1,2].
Strings are quoted, so they no longer collide with null, booleans, numbers or arrays, and colons inside string values can no longer be confused with the key separator.
Objects are still stringified through __toString() as before.

Breaking changes

None. Keys for integer and array arguments are unchanged.
Cache entries for fields with string, boolean or null arguments get new keys, so they are recomputed once after upgrading.

Changelog

Fixed

• Encode argument values unambiguously in @cache keys, so null, booleans and strings no longer share cache entries

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

[Copilot]

🟡 Changes recommended

The new encoding makes null collide with the literal string "null", allowing queries to receive incorrect cached results.

1 open issue

• Distinguish null and string values in cache keys · New

_{Review effort: Balanced}

[sk4rp]

@spawnia fixed in b84a06a.
All non-object argument values are now JSON encoded, so strings are quoted (arg:"null") and can no longer collide with null, booleans, numbers or arrays.
Objects are still cast through __toString() as before.
Added regression tests for null vs "null" on the key generator and on a @cache field.