Issue Feature Closed

#109412Auto-discovery of EXT:form YAML configurations

Josua Vogel 03/27/26, 20:46 updated 03/31/26, 08:09

Description

YAML configuration files for the TYPO3 Form Framework are currently registered manually via TypoScript in ext_localconf.php or setup.typoscript, requiring separate registrations for frontend and backend. This is error-prone, uses TypoScript as a mere file path transport (an abuse of the mechanism).

The proposal is to replace this with a convention-based directory auto-discovery, modelled after the Site Sets pattern.

*Proposed Solution*
Introduce auto-discovery of form YAML configuration files from the directory EXT:*/Configuration/Form/ across all active extensions.

EXT:my_extension/
Configuration/
Form/
MyFormSet/ ← arbitrary sub-directory name
config.yaml ← required: set metadata
setup.yaml ← optional: form config (FE + BE)

An extension may ship multiple sets in separate sub-directories.

config.yaml — Set Metadata

# Unique identifier following vendor/name convention
name: my-vendor/my-form-set

# Human-readable label for diagnostic output
label: 'My Custom Form Set'

# Merge priority: lower = loaded first (acts as base).
# EXT:form core set uses priority 10. Extension sets default to 100.
priority: 200

*Merge Order*
Files are sorted by ascending priority. Each file is merged on top of the previous one using array_replace_recursive, identical to the former TypoScript-based behaviour.

*Disable Mechanism*
Because all sets from all active extensions are loaded automatically, a global opt-out is available:

$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['form']['disabledSets'][]
    = 'some-vendor/conflicting-set';

Matching is done against the name field in config.yaml, not the directory name.

Reviews 5