[lazerg]

Fixes #1198

When a keyed collection (array<string, ChildData>) has array keys containing literal dots, validation reports the fields as missing. The static rules path added in #1043 builds the rule key from the raw array key, so key.with.dots gets treated as nested path segments (items.key.with.dots.string) instead of one key.

This escapes the dots in the collection key so the rule key becomes items.key\.with\.dots.string, matching how the dynamic Rule::forEach path already handles it.

[ropi-bc]

Thanks for jumping on it

[lazerg]

Hi @rubenvanassche, just a gentle follow-up. It has been two weeks since my last ping. Could you take a look when you have a moment? Thanks!

[cativo23]

Found the same fix working #1198 and saw this after. Going to open a PR with the same one-line change plus a regression test, linked from here. All credit for the diagnosis is yours — if you'd rather reopen this one instead, happy to hand over the test.

[lazerg]

Go ahead with #1206. No need to reopen mine, since yours already carries the regression test.

The diagnosis holds. #1043 builds the rule key from the raw array key, so a literal dot becomes a path separator. The Rule::forEach path escapes it already, which is why an empty rules() hides the bug. Escaping inside resolveStaticCollectionRules is the right spot, because ValidationPath is also used for MapName and rule keys that contain dots on purpose.