TomasVotruba
commented
1 year ago Hi, the rule is gone, as it was tailored for single case in single project and not really practical/reliable anymore.
Could you send a PR to update the post? https://github.com/tomasVotruba/tomasvotruba.com/
We mostly changed the next/prev/parent logic, but the rest should have an upgrade path - https://getrector.com/blog/rector-017-brings-more-robust-and-lighter-node-tree
It might be useful to follow Rector blog to learn about news and what was changed: https://getrector.com/blog
Hi, Maybe it's not the best place for that issue, as I've found the link in the article that has broken code samples, but the issue is a bit bigger.
I've tried following this article and found that there is no
switch-formatcommand anymore that is not a big deal. But also the rector config provided there doesn't work as the class doesn't exist, and I can't find an alternative rector for it.The BC issue is a bit more general for me. I've read your book and then used Rector to write some rules for the project based on 0.16.0 that was the current version.
And now I literally can't upgrade the package without significant refactoring because some classes the package relies on are deleted, others are changed a lot and there are not alternatives, as I understand, some features, crucial for the rules I need do not exist anymore. I can always stick to the old version of Rector, but this is a bad long time strategy for me.
Maybe you have some recommendations or can share the plans, when the stable version of Rector will be available.
Thank you.