Repository navigation
[MAINTENANCE] Standardize all default configurations to YAML - #2227
Open
beatrycze-volk wants to merge 7 commits into
Open
beatrycze-volk wants to merge 7 commits into
beatrycze-volk wants to merge 7 commits into
Conversation
Removes the explicit TypoScript retrieval for validation settings. The controller now uses its already available $this->settings property for this configuration. This change also generalizes the 'domDocumentValidation' access by removing the hardcoded 'dfgviewer' sub-key.
…ion to YAML Rename the 'ValidationForm' plugin and its associated files to 'Validation' to better match TYPO3 plugin naming convention. Refactor the validation configuration mechanism by moving validation rules from TypoScript settings into dedicated YAML file. This improves modularity and maintainability by introducing a `YamlConfigurationProvider` for loading configurations, making them more declarative and easier to manage.
… and plugin rename Reflects the migration of DOMDocumentValidation middleware configuration from TypoScript to YAML files and the renaming of the 'Validation Form' plugin to 'Validation'. This ensures the documentation accurately describes the current setup.
Migrate existing default data for formats, metadata, and structures from JSON files to dedicated YAML configuration files. These configurations are now loaded through the `YamlConfigurationProvider`. The `YamlConfigurationProvider` itself has been generalized and moved from the `Validation\Configuration` namespace to a more generic `Configuration` namespace to reflect its broadened role. This includes introducing specific methods like `getTenantConfiguration` and `getValidationConfiguration` for clearer access to different configuration types. ```
beatrycze-volk
added
the
⟳ maintenance
This branch has not been deployed
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
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.
Migrate existing default data for formats, metadata, and structures from JSON files to dedicated YAML configuration files. These configurations are now loaded through the
YamlConfigurationProvider.The
YamlConfigurationProvideritself has been generalized and moved from theValidation\Configurationnamespace to a more genericConfigurationnamespace to reflect its broadened role. This includes introducing specific methods likegetTenantConfigurationandgetValidationConfigurationfor clearer access to different configuration types.Depends on #2214