Always use YamlSymfony for loading service yaml files

Created on 15 January 2024, 6 months ago
Updated 3 March 2024, 4 months ago

Problem/Motivation

From #3108309-29: Support Yaml::PARSE_CUSTOM_TAGS in \Drupal\Component\Serialization\YamlSymfony::decode β†’

Re #27 I was tempted to suggest that. I was reticent because service.yml files are one of the thing parsed on cold cache. But the more I think about it the more I think that this is a good approach for now. The capabilities of the YAML parser and container configuration are quite closely related so this does not feel like a bad decision - also we use FileCache here so potentially this has no impact on cold cache as that can persist across a cache rebuild.

Trying to duplicate custom tag support from upstream Symfony in both the YamlSymfony and YamlPecl serializers is becoming increasingly complex. Let's save ourselves the headache and only use YamlSymfony for service yamls.

Steps to reproduce

Proposed resolution

Only use YamlSymfony for service yamls.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Closed: outdated

Version

11.0 πŸ”₯

Component
BaseΒ  β†’

Last updated less than a minute ago

Created by

πŸ‡¦πŸ‡ΊAustralia kim.pepper πŸ„β€β™‚οΈπŸ‡¦πŸ‡ΊSydney, Australia

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.69.0 2024