Register simple Customizer fields natively

[Copilot]

Kirki is being retired from Municipio, so simple 1:1 Customizer fields should use native WordPress controls where possible. Complex Kirki-specific fields remain on Kirki for follow-up work.

• Native field registration

  • Routes simple fields through customize_register.
  • Supports native-compatible types such as select, radio, text, textarea, checkbox, number, url, color, image, and upload.
  • Keeps fields with Kirki-specific options on Kirki::add_field().

• Applicator compatibility

  • Exposes native field definitions to existing Customizer applicators.
  • Reads native field values via get_theme_mod() while preserving Kirki value reads for complex fields.

• Focused coverage

  • Adds tests for native-field detection and native setting/control registration.

KirkiField::addField([
    'type'     => 'select',
    'settings' => 'column_size_left',
    'label'    => esc_html__('Left', 'municipio'),
    'section'  => $sectionID,
    'default'  => 'normal',
    'choices'  => [
        'normal' => esc_html__('Normal', 'municipio'),
        'large'  => esc_html__('Large', 'municipio'),
    ],
]);

Simple fields like this are now registered as native WordPress Customizer controls instead of Kirki fields.

[sonarqubecloud]

Quality Gate passed

Issues
6 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