Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
YamlFileLoader
was copied from Symfony 2.3. We updated to 2.4, but missed the literal copy.
I investigated whether it is possible to extend Symfony's instead of copying, but no luck:
https://github.com/symfony/symfony/pull/10920
For now, let's just simply update the code with latest upstream code.
Note that this intentionally violates Drupal coding standards. The code is a literal copy from upstream.
Comment | File | Size | Author |
---|---|---|---|
#3 | di.yamlfileloader.3.patch | 17.64 KB | sun |
drupal8.yamlfileloader.0.patch | 17.49 KB | sun | |
Comments
Comment #1
sundrupal8.yamlfileloader.0.patch queued for re-testing.
Comment #3
sunMerged 8.x.
Comment #4
znerol CreditAttribution: znerol commentedReading the patch and also the pull-request, this is indeed an unfortunate situation. Would it help when the meat of the class would be extracted into a trait upstream? It looks to me that we just might want to reuse
parseDefinition[s]()
andresolveServices()
.Other than that the patch looks ok.
An idea for a follow-up: Perhaps it would be possible to extract the static caching into a wrapper class in order to further align the actual
YamlFileLoader
with upstream. Not sure how much that helps though.Comment #6
catchThis is irritating but I don't have better suggestions atm. Committed/pushed to 8.x, thanks!
Comment #8
znerol CreditAttribution: znerol commentedOpened #2375339: Update DependencyInjection YamlFileLoader for Symfony 2.6