Problem/Motivation

Right now this list is hard-coded in \Drupal\automatic_updates\Updater::getCorePackageNames()

but we don't want to have to update that any time we add a new plugin to core.

Proposed resolution

Ideas for how to get the list

  1. hard coded
    1. a. in module
    2. b. 1 place in core (code write a test to fail if plugin/metadata package added but not added to 1 place)
    3. c. in project template metadata.(might be removed on a site)
  2. remote request
    1. request current project template on code.drupal.*
    2. Add API endpoint on drupal.org
  3. heuristic: rely on drupal/core-* names
  4. plugins declare themselves part of core

Remaining tasks

User interface changes

API changes

Data model changes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tedbow created an issue. See original summary.

phenaproxima made their first commit to this issue’s fork.

phenaproxima’s picture

Title: Determine how to identify composer core packages » Determine how to identify core Composer packages
Status: Active » Reviewed & tested by the community

RTBC based on verbal approval from @tedbow.

phenaproxima’s picture

  • phenaproxima committed 418d7f2 on 8.x-2.x
    Issue #3242626 by phenaproxima, tedbow, TravisCarden: Determine how to...
phenaproxima’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.