Add a generic config option allowRisky which defaults to false.
This option should be respected by all sniffs which do something which could be considered risky, i.e. might cause parse errors or unit tests to fail as the code change is more involved.
The option could be set using either --runtime-set allowRisky true or by adding <config name"allowRisky" value="true"/> to a custom ruleset.
Levels of riskiness
Alternatively, based on the same principle, a granularization could be added using numeric riskiness levels
My current line of thinking would be:
0 being non-risky;
1 being a little risky, but will probably be OK;
2 code will always need manual review after the fixer has run;
Add a generic config option
allowRiskywhich defaults tofalse.This option should be respected by all sniffs which do something which could be considered risky, i.e. might cause parse errors or unit tests to fail as the code change is more involved.
The option could be set using either
--runtime-set allowRisky trueor by adding<config name"allowRisky" value="true"/>to a custom ruleset.Levels of riskiness
Alternatively, based on the same principle, a granularization could be added using numeric riskiness levels
My current line of thinking would be:
0being non-risky;1being a little risky, but will probably be OK;2code will always need manual review after the fixer has run;3possibility of parse error being introduced.Opinions welcome!