Provide optional support for using composer.json for dependency metadata

Open on Drupal.org →

Created on 8 October 2018, about 6 years ago

Updated 16 May 2024, 7 months ago

Problem/Motivation

Issues we're trying to solve

core: 8.x in an info file is restrictive
we invented our own dependency syntax that is overly complex because of the optional core major version
we want to move away from having the major version in the module version (e.g. 8.x-1.x » 1.0.0)
we want to move core away from version: VERSION so we can do subtree splitting
we want contrib modules to be able to declare their composer dependencies - e.g my module 1.3 needs symfony/yaml 4.0
as a bonus, themes could rely on modules

Proposed resolution

use composer.json for

discovery of themes/modules/profiles/engines
dependency declaration
version numbering

Deprecate the dependencies, type and version keys in info.yml files

Remaining tasks

Wind back to the scope of comment #39

User interface changes

API changes

Data model changes

✨ Feature request

Status

Needs work

Version

11.0 🔥

Component

Extension →

Last updated 6 days ago

No maintainer

Created by

🇨🇦Canada jibran Toronto, Canada

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.

mwds2019

Needs tests
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Needs issue summary update
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Needs release manager review
It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.

Automatic Updates Initiative

Incomplete comments

Merge Requests

!8094Provide optional support for using composer.json for dependency metadata
Open
🇫🇷France Grimreaper
updated 7 months ago

Comments & Activities

Not all content is available!

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

First commit to issue fork.
Merge request !8094Draft: Issue #3005229 by tedbow, larowlan, Mile23, shaal, Mixologic, Wim Leers, xjm,... → (Open) created by Grimreaper
Pipeline finished with Failed
7 months ago
Total: 195s
#174091
Pipeline finished with Failed
7 months ago
Total: 180s
#174117
Comment 7 months ago →
🇫🇷France Grimreaper France 🇫🇷
Hi,

I tried to convert patch from comment 117 into a MR to more easily update it.

After trying to figure out in more details what it is was doing, I think I will open a separated issue for #3440128: version in info.yml for general project → .

In my case, I only want to try to extract versions from Composer if not present in .info.yml to provide site admin versions in admin pages.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024