Guard Gutenberg block data handling against array-valued ACF fields

[Copilot]

Municipio\Admin\Gutenberg\Blocks\BlockManager assumed all block data values were strings and called str_contains() unconditionally. Container/block data coming from ACF can include arrays, which caused runtime type errors during render and validation.

• Runtime guard for mixed block data

  • Add string checks before resolving field references in buildData()
  • Preserve non-string values as-is so array-backed block fields continue through the render path unchanged

• Validation hardening

  • Apply the same string guard in validateFields()
  • Only treat actual ACF field keys as resolvable/validatable references
  • Avoid descendant checks on non-string parent values

• Regression coverage

  • Add focused tests for:
    • array-valued block data passed into buildData()
    • arrays containing field-like strings that should not be resolved implicitly
    • required-field validation still working when mixed with array-valued data

if (is_string($value) && str_contains($value, 'field_')) {
    $newData[$key] = get_field($value);
}

[sonarqubecloud]

Quality Gate passed

Issues
8 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud