Confusing duplication of container parameters in core.services.yml and default.services.yml

Created on 31 July 2015, almost 9 years ago
Updated 5 March 2024, 4 months ago

Problem/Motivation

AFAICT we only duplicate all of our default container parameter values from default.services.yml to core.services.yml for KernelTestBase tests.

Why not just let KTB use that YML file, just like WTB already does?

This is very confusing. Not in the least because you have to keep those two places in sync. It's also a WTF, because developers won't know how to interpret these seemingly identical things β€” I know I don't.

Proposed resolution

Make this more sane :)

Remaining tasks

TBD

User interface changes

None.

API changes

None.

Data model changes

None.

πŸ“Œ Task
Status

Active

Version

11.0 πŸ”₯

Component
DocumentationΒ  β†’

Last updated about 5 hours ago

No maintainer
Created by

πŸ‡§πŸ‡ͺBelgium Wim Leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

Live updates comments and jobs are added and updated live.
  • DrupalWTF

    Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¬πŸ‡§United Kingdom joachim

    > The reason is that default.services.yml is there is to have a place to document values and what you could change them to, similar to settings.php

    > Yes, default.services.yml isn't ever used.

    This and the rest of #2 should be addedf to default.services.yml as documentation.

Production build 0.69.0 2024