Skip to content

Expose explicit native Rector refactoring as a separate command #46

Closed

Description

@coisa

Add an opt-in POPO AsCommand semantic refactoring entrypoint in this tool, separate from check/fix and using published native Rector configuration. Dry-run by default; application only through an explicit option. No implicit migration sets or host-PHP target assumption. Qualify native behavior for empty/invalid rules/config, no project config generation, exact exit codes, target PHP, caches and consumer/tool autoload collisions. Use existing process transport and published dependencies, no parallel framework/DSL. This is a future-minor candidate, not a blocker for already published0.1.0; issue4 remains open for full custom PHPDoc/semantic policy.

Activity

  1. coisa commented on Oct 27, 2026

    @coisa
    ContributorAuthor

    Delivered by PR #52, merged normally as 77540ecbf17e2238f77016f7c31660d60461763e. The final PR HEAD 5700df9 had successful PHP 8.3/8.4/8.5 checks and completed current-HEAD Codex code/security and CodeRabbit review, with all findings corrected or resolved with verified native-version evidence.

    The separate POPO/AsCommand refactor command requires explicit native configuration, effective rules and a PHP target. Dry-run is the default; --apply writes and then verifies. Target/config/cache/autoload boundaries, invalid inputs, exits, finite timeout overrides and cleanup are regression-tested. check/fix remain independent of Rector. Main Quality run 40446934662 and Changelog run 40446936432 completed successfully after integration.

    This completes this command issue; #4 stays open for custom PHPDoc-rule extraction/parity. The automatically prepared version PR is separate; no tag/release is claimed here.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions