Skip to content

Conversation

@nicolas-grekas
Copy link
Member

Q A
Branch? 8.0
Bug fix? no
New feature? yes
Deprecations? no
Issues -
License MIT

Per #60568

$locatorPass = new ServiceLocatorTagPass();
$locatorPass->process($container);
}
$dumpedContainer = unserialize(file_get_contents(substr_replace($file, '.ser', -4)));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest changing the value of debug.container.dump to have a file name ending in .ser directly instead of keeping a .xml path while the XML file won't exist.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd keep the param as is: the xml file still exists and is dumped e.g. for IDE plugins

Copy link
Member

@yceruto yceruto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

nicolas-grekas added a commit that referenced this pull request Oct 2, 2025
…ML loaders are removed (nicolas-grekas)

This PR was merged into the 7.4 branch.

Discussion
----------

 Ensure branch 7.4 will remain compatible with 8.0 once XML loaders are removed

| Q             | A
| ------------- | ---
| Branch?       | 7.4
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

After #60568
Needed for #61930

Commits
-------

758c7f5 Ensure branch 7.4 will remain compatible with 8.0 once XML loaders are removed
@nicolas-grekas
Copy link
Member Author

PR ready, failures unrelated

@ro0NL
Copy link
Contributor

ro0NL commented Oct 2, 2025

does this also include the removal of var/cache/env/*Container.xml?

@nicolas-grekas
Copy link
Member Author

It doesn't (see #61930 (comment))

@ro0NL
Copy link
Contributor

ro0NL commented Oct 2, 2025

so IIUC we preserve XML format on that location for the future?

@nicolas-grekas
Copy link
Member Author

Correct, see #61280

@ro0NL
Copy link
Contributor

ro0NL commented Oct 2, 2025

im struggling why we couldnt maintain the format then for every day config, personally i dont mind lack of xsd valition nor requiring ext-dom (in userland)

@nicolas-grekas
Copy link
Member Author

The discussion happened in #60568

@ro0NL
Copy link
Contributor

ro0NL commented Oct 2, 2025

Let's wait on the discussion on the issue to know what should actually be deprecated. This PR deprecates a lot more than what was mentioned in the issue it fixes.

I am not really sure we need to go thus far.

But if someone likes using XML config files, why shouldn't we allow it optionally if the maintenance overhead is barely measurable?

I have a hard time following this initiative to be honest.

@nicolas-grekas
Copy link
Member Author

This is really not helping @ro0NL, please do your part, this is burning my good will.
The discussion goes on to reduce the scope - that comment you copy/pasted is related to a previous iteration of the PR, you can see that from the rest of the discussion.

@ro0NL
Copy link
Contributor

ro0NL commented Oct 2, 2025

perhaps, but enforcing a full format migration like that, is not what i was waiting for

@ro0NL
Copy link
Contributor

ro0NL commented Oct 2, 2025

we have 3 years of hoping the migration tool will do it's job, so OK.

@fabpot
Copy link
Member

fabpot commented Oct 3, 2025

Thank you @nicolas-grekas.

@fabpot fabpot merged commit 3ce1fa9 into symfony:8.0 Oct 3, 2025
5 of 10 checks passed
@nicolas-grekas nicolas-grekas deleted the drop-xml-config branch October 3, 2025 06:27
@fabpot fabpot mentioned this pull request Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants