GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add new "common" schematic to share configurations for all schematics at once · Issue #33221 · angular/angular-cli

Add new "common" schematic to share configurations for all schematics at once #33221

New issue
Copy link
New issue
Copy link
Open
Open
Add new "common" schematic to share configurations for all schematics at once#33221
Copy link
Labels
area: @angular-devkit/schematicsgemini-triagedLabel noting that an issue has been triaged by geminiLabel noting that an issue has been triaged by gemini

Description

@Maryannah
Maryannah
opened on May 20, 2026
Issue body actions

Command

generate

Description

Implement an internal artifact to commonize the configuration of schematics so that all schematics can share a common configuration by default, and override on a per-artifact basis if needed. Currently, all configurations are duplicated, and while not that annoying to deal with for a single collection, it can quickly add up when using several collections.

Describe the solution you'd like

Actual :

{
  "schematics": {
    "@schematics/angular:component": { "skipSelector": true },
    "@schematics/angular:directive": { "skipSelector": true },
    "@schematics/angular:pipe": { "skipSelector": true }
  }
}

Proposed :

{
  "schematics": {
    "@schematics/angular:common": { "skipSelector": true }
  }
}

This new common schematic would contain either

  • only fields that are common to all artifacts
  • All fields possible, even if not applicable to certain artifacts

Resolving would follow this pattern :

  • Look for common artifact schematic value
  • If existing, apply value
    • If all fields are possible : also check if value is applicable to artifact
  • Look for direct artifact schematic value
  • Override value

Describe alternatives you've considered

Doing it by hand as already done today is the only solution

Activity

  1. angular-robot
    added
    area: @angular-devkit/schematics
    gemini-triagedLabel noting that an issue has been triaged by geminiLabel noting that an issue has been triaged by gemini
    on May 20, 2026
  2. Maryannah commented on Jun 14, 2026

    @Maryannah
    Maryannah
    on Jun 14, 2026
    Author
    More actions

    Hello, any news on that matter ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: @angular-devkit/schematicsgemini-triagedLabel noting that an issue has been triaged by geminiLabel noting that an issue has been triaged by gemini

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.