Rector is such a great tool, it does so much great stuff that for big projects it's very challenging to run, and more important, review changes... so here is my 2 ideas that would improve DX drastically on big projects....
I know this probably can be achieved creating different config files, but bear with me 😄
Get Rules
Create a command like rector get-rule-list, which just returns a list of all rules, one per line...
Rule Multiple Option
Like add rector process --rule=a --rule=b, so we can force to just one or a few rules per time.
My idea / workflow is:
play with config
get the rules
run one by one and commit separately
So it can be easier to review / evaluate...
Yay or Nay?
I would be open to make a PR for that, just want to confirm the idea is good or i didn't miss any existing feature.
Rector is such a great tool, it does so much great stuff that for big projects it's very challenging to run, and more important, review changes... so here is my 2 ideas that would improve DX drastically on big projects....
I know this probably can be achieved creating different config files, but bear with me 😄
Get Rules
Create a command like
rector get-rule-list
, which just returns a list of all rules, one per line...Rule Multiple Option
Like add
rector process --rule=a --rule=b
, so we can force to just one or a few rules per time.My idea / workflow is:
So it can be easier to review / evaluate...
Yay or Nay?
I would be open to make a PR for that, just want to confirm the idea is good or i didn't miss any existing feature.