Remove development.services.yml from Drupal's composer scaffolding

Created on 15 November 2019, over 4 years ago
Updated 5 May 2023, about 1 year ago

During development, example.settings.local.php is frequently duplicated and used as is, or with minor modifications. One of the lines that's included by default is enabling local development services. Editing this file to turn on twig debug or disable caching is a common step in the development process.

However, because this file is part of Drupal's composer scaffolding, it is overwritten back to its default value any time core is updated via composer.

We should remove this file from core scaffolding so that local development modifications aren't overwritten by composer actions

Original Title & Issue Summary:

Rename development.services.yml to example.development.services.yaml

During development, example.settings.local.php is frequently duplicated and used as is, or with minor modifications. One of the lines that's included by default is enabling local development services. Editing this file to turn on twig debug or disable caching is a common step in the development process.

However, because this file is part of Drupal core, it is overwritten back to its default value any time core is updated via composer.

I would propose renaming development.services.yml to [example/default].development.services.yml while leaving the rest of the related core files as is. This would encourage developers to create a new file not included in core that is therefore not overwritten during the update process.

✨ Feature request
Status

Needs work

Version

10.1 ✨

Component
BaseΒ  β†’

Last updated 1 minute ago

Created by

πŸ‡ΊπŸ‡ΈUnited States andy-blum Ohio, USA

Live updates comments and jobs are added and updated live.
  • Needs framework manager review

    It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

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.

Production build 0.69.0 2024