AI disclosure
AI-Generated: Yes (Used Cursor to draft this issue summary).
Problem/Motivation
Drupal 11.4+ includes Doctor (vendor/bin/dr). Drush 15 routes most Drush commands through dr and stops maintaining several namespaces, including field:*.
Drush still has mature field:* implementations (src/Commands/field, tested in FieldTest.php). Nothing in core Doctor replaces that toolkit today. Teams adopting dr need a supported place to run field introspection and configuration from the CLI—but it is unsettled whether that belongs in core Doctor or in a contrib module registered with dr.
This plan issue agrees on the target home and ownership before anyone ports commands.
Steps to reproduce
- Drupal 11.4+ with Drush 15.
vendor/bin/dr list— nofield:*commands.- Attempt former Drush workflows (
field:info,field:create, etc.) viadr.
Expected: A documented, supported location (core or contrib) for field:* on dr.
Actual: No agreed owner; Drush 15 does not maintain field:* long term.
Proposed resolution
Phase 1 — Decide (this issue). Choose one primary home and document rationale. Likely options:
- Core Doctor —
field:*ships with Drupal; same review bar and release cycle as otherdrcommands; larger core maintenance surface (especiallyfield:create). - Contrib — a supported module (new or existing) registers Symfony Console commands with Doctor; optional via Composer; core stays smaller; sites must require the package explicitly.
- Split — e.g. discovery commands (
field:types,field:widgets,field:formatters) in core, destructive or complex CRUD in contrib (only if the issue thread prefers a narrow core scope).
Decision inputs: parity with Drush behavior, security and destructive-operation policy, test burden, overlap with Field UI, whether “every developer CLI” belongs in core vs optional tooling, and how Drush 15 documents migration when field:* is gone.
Phase 2 — Port (child issues). After Phase 1, open children only on the chosen project (core or contrib). Scope: field:create, field:delete, field:info, field:base-info, field:base-override-create, field:types, field:widgets, field:formatters. Use Drush 15.x as the behavioral baseline; implement as plain Console commands for Doctor.
If the decision is contrib-only, close or narrow this core plan and link the contrib meta issue; do not land command implementations in core.
Remaining tasks
- [ ] Thread: core vs contrib vs split — record conclusion on this issue.
- [ ] Identify contrib candidate (new project vs existing) if contrib wins.
- [ ] Align with CLI subsystem maintainers and Drush maintainers (Drush 15 post).
- [ ] After decision: open child issues on the correct tracker with Parent set appropriately.
- [ ] Document where
field:*live fordrusers (core docs and/or contrib README).
User interface changes
None.
Introduced terminology
Doctor — core Symfony Console application behind vendor/bin/dr. Contrib commands can register with Doctor without living in core.
API changes
To be determined. Depends on Phase 1: new core dr commands, contrib-only Console commands, or a split.
Data model changes
None.
Comments