You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rector has a few rectors that handle adding types based on the other information in the class or IN the called methods from other classes. My plan is to add as many types as possible to my code base in a few steps. The first step is to add types where I am 100% confident the type is valid and go straight to the production.
So my question is which Rectors handling types can be described as 100% sure. Maybe we should add this information to the rules overview?
Btw. What do you think about globally introducing the concept of safe/risky Rector? PHP-CS-Fixer uses this concept and this is very helpful when you know whether a fixer is safe or risky.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Rector has a few rectors that handle adding types based on the other information in the class or IN the called methods from other classes. My plan is to add as many types as possible to my code base in a few steps. The first step is to add types where I am 100% confident the type is valid and go straight to the production.
So my question is which Rectors handling types can be described as 100% sure. Maybe we should add this information to the rules overview?
Btw. What do you think about globally introducing the concept of safe/risky Rector? PHP-CS-Fixer uses this concept and this is very helpful when you know whether a fixer is safe or risky.
Beta Was this translation helpful? Give feedback.
All reactions