Feature/php fixer

[ashucg]

Added a new separate option to define PHP-CS-Fixer options/parameters allowing users to easily switch back to the former (phpF) if they want to

Example usage:

{
    "codeformatter_php_options": {
        "syntaxes": "php",

        // will be neglected because "passes_option" is defined
        "passes": ["AliasToMaster", "AlignDoubleArrow"],
        
        // php-cs-fixer will be used with these parameters
        // you can define empty object i.e., "passes_option": {} to use the former
        "passes_option": {
            "@PSR2": true,
            "blank_line_after_namespace": true,
            "concat_space": {
                "spacing": "none"
            },
            "array_syntax": {
                "syntax": "short"
            },
        },
    },
}

[akalongman]

Is it backward compatible with current config?

[ashucg]

I have not removed passes option from config so that users can switch between phpF and PHP-CS-Fixer. I have mentioned this under Example usage. I have not added documentation for PHP-CS-Fixer options because there are a lot of options to cover.

PS: sorry for replying this late

[akalongman]

@ashucg do you still use this package?

[ashucg]

@akalongman yes, I do

[akalongman]

@ashucg could you help to migrate PHP formatting part from phpF to PHP Code Fixer entirely?

[ashucg]

@akalongman sure, I can help with that.

[ashucg]

Hi @akalongman,

I think I will have some spare time in December and I will finally get to work on migration part.

I was thinking about creating predefined rules using a dictionary to map phpF options to php-cs-fixer and after formatting the code, tell users to check console output for recommended php-cs-fixer options which they can simply copy and add to their User Package Settings . This would help users to get a working installation without going through php-cs-fixer's available options just to get a similar configuration.

Let me know your thoughts about the whole process.

[akalongman]

@ashucg I like your approach 👍