Repository navigation
[FEATURE] List type transformers in the Configuration module - #77
Merged
Merged
Conversation
Expose every registered type transformer with its inputs, defaults, controls, injected service types and priority so developers can inspect which registration is selected and which ones have been overridden. Register the provider when lowlevel is available and cover installations with and without the extension. Require lowlevel only for development so the provider tests run in the standalone extension's CI setup.
Format booleans, null and empty strings for TYPO3's Configuration tree and distinguish missing defaults from explicitly declared null defaults. Apply the display formatting recursively while preserving array keys, scalar values and enum defaults. Cover the rendered HTML through TYPO3's actual ConfigurationController and verify that transformer arguments and execution retain native values.
Show enum cases explicitly in the Configuration module so a backed enum with an empty string value remains visible. Apply the same formatting to enums in nested array defaults. Cover TypolinkTargetEnum::none in the built-in transformer and the real TYPO3 tree renderer while preserving native enum values for execution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Frontend Studio: Type transformers to TYPO3's System → Configuration module so developers can inspect the transformers registered in their project.
Group all registrations by return type and show the handler, method, priority, active registration, input types, required flags, defaults, control overrides, and injected service types.
Keep overridden registrations visible and exclude cached type lookups from the list.
Register the provider when
lowlevelis available and addtypo3/cms-lowlevelas a development dependency for the tests.Cover installations with and without the extension and document where to find the configuration.
Verified in an isolated checkout with PHP 8.5 and TYPO3 14.3.9:
CI=true ./Build/Scripts/runTests.sh -p 8.5 -s unit— 1,060 tests passed.CI=true ./Build/Scripts/runTests.sh -p 8.5 -s grumphpRun— passed, including PHPStan, Rector, style checks, Composer validation, and security audit.CI=true ./Build/Scripts/runTests.sh -p 8.5 -s functional -d sqlite -- Tests/Functional/ConfigurationModuleProvider— both integration tests passed.The MySQL integration attempt was blocked because the runner's database container did not become ready on port 3306.