New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 4 BC idea list #6155
Comments
This ☝🏼 and the priorities. I'm thinking about creating in interface NewFixerInterface extends FixerInfertace
{
public function getFixersToRunAfter(): array {}
} and deprecate The runner then will get the list of fixers somehow sorted (like we have the fixer that always run first) and after running every fixer will have a list of fixers still to run and will update that list with This will solve problem of circular priorities which now cannot be addressed. But, it will bring new problems - performance (how much will that slow down the fixer? Some fixers might need to run multiple times) and how to handle situation when set of fixers reverts each others and are still on a list of fixers to be run? Or, maybe we do not want to have |
proposal - let's create a label/milestone marker for BC breaks and have a way to discuss each idea separately. otherwise it will be a mess with constant changing of WHICH bc break we discuss |
@SpacePossum for the transformers what about BC break for the interface? It's not a problem if 4.0 will be fot PHP 8+ only. |
|
Hi all,
Basically I would like to share a list of v4 BC ideas I got. Mainly to get feedback and see what others think.
I would like to have custom tokens for all different types of usages of the following symbols.
:
:goto
T_TYPE_COLON
, listed here for completeness)CT::T_NAMED_ARGUMENT_COLON
, listed here for completeness)switch-case
&
:$b = &$a;
)CT::T_TYPE_INTERSECTION
, listed here for completeness)CT::T_RETURN_REF
, listed here for completeness)|
:I would like the exit code to changed when a file got fixed or needs fixing. If the fix is done successful the tool currently ends with exit code 0 unless running with the
dry-run
flag, I would like this exception to go away and not exit with code 0.In general to have a look at single use classes to see if it makes sense to not merge these (for example
NamespacedStringTokenGenerator
) with the caller/use class.Deprecate FinalClassFixer in favor of FinalInternalClassFixer - #6128
Drop alternative syntax by default for all build in fixers - #6003
start looking for external library managing types parsing for PHPDocs
#6063 (comment)
CT type of the
enum
case
vs.swtich
case
The text was updated successfully, but these errors were encountered: