-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[RFC] Deprecate and remove support for semantic XML configuration #60200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
What do you mean by "it"?
I agree but I really didn't see any project using it. More over, this configuration formation is painful to use (event for end user) And Doctrine has already removed a configuration format. So there is a precedent 😃 |
This is not trivial as there is some transformations of the input before validating the configuration (example in DoctrineBundle) that requires a specific schema file. We hit this issue while trying to generate the JSON schema configuration in #59620
We can decide to deprecate this format and possibly reconsider this decision before deleting it, if people contest with specific use cases. |
I'd like to, but I don't know where we could put it to reach the maximum number of people. |
During https://live.symfony.com/ |
Description
Maintaining https://github.com/symfony/symfony/blob/7.3/src/Symfony/Bundle/FrameworkBundle/Resources/config/schema/symfony-1.0.xsd is not easy.
And I never saw a project using XML to configure the framework.
So I propose to remove this support. I know it's always heartbreaking to remove a feature, but I really think it's much better for Symfony maintainers.
More over, we now have much better format to configure the framework...
Example
No response
The text was updated successfully, but these errors were encountered: