Replies: 1 comment 1 reply
-
You may can look at this PR for inspiration: actually, renaming identifier that can be accessed by outside, eg: public method or public property/constant, you need to ensure: It not 3rd party code that not part of "paths" that set via command line or |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey team Rector ... just had a question that I really couldn't find a solid answer to anywhere.
So one task I was hoping/planning on doing with PHP Rector in a repo that I'm working on, is using it to safely refactor some snake_case methods/properties into PSR-12 compliant camelCase ones.
But I ran into the fact that every bit of documentation you can find about using Rector to do this (of which there are lots of references on the web about it) ... all refer to code from the pre-2020 era of PHP Rector ... and rules that no longer exist that used to do this (it would seem).
As far as I can tell. There are currently no rules that come with Rector that could do this task ... nor can I find any existing packages that have written custom rules to do this either. While I could write my own obviously. The goal here was to end up using a 'trusted tool' with a 'trusted rule' that had been battle-hardened (at least, used by 1 other person at a minimum) ... to rely on versus doing it by hand.
But also ... I can't find any actual discussion anywhere as to why exactly the PHP Rector rules that used to exist to do this, appear to be removed.
Was hoping to just find out and get documented here in a Discussion:
Thanks
Beta Was this translation helpful? Give feedback.
All reactions