The only request I have from looking at the output it produced from my code:

When I’ve got multi-dimensional key-value arrays declared on multiple lines it turns them into a single line. I would like to see an options to make this go the other way ie. take a single line array and format it over multiple lines for better readability, and leave existing multiple line array declarations as is (or tidy up the indenting if required).

eg.
$myVar = array(
‘key’ => ‘value’,
‘key’ => array(
‘key’ => ‘value’,
‘key’ => ‘value’,
),
);

Also, +1 for open sourcing this as I’m sure many developers would like to convert this into a macro/plugin for their development IDE of choice…

At the moment I have 7 points where I have improvements:

1. The ending php tag “?>” has a [TAB] in front. (not in the same level as the opening tag). Usually if I have no TAB before the beginning “”.

2. “while (true)[NEW LINE]{” will be converted into “while (true){”. Usually we should have a space between “)” and “{”.

3. If the user enables an optional setting, the cleaner could also remove line-breaks in multi-lined-strings. Example:

Your result at the moment:

[TABs]echo ‘This is a very long string.[CRLF]
Yes, it also needs a second line.’;

I think, this is better:

[TABs]echo ‘This is a very long string.’.”\r\n”.[CRLF]
[TABs+1]‘Yes, it also needs a second line.’;

But be careful with the “\r\n”.
a) If in the original file there has no CRLF at this linebreak, then it shouldn’t be a “\r\n”. It should be the line-break-style the original file had.
b) If the string which is broken is a double-quoted string (”…”), then we can insert the \r\n IN the string and do not need a concatenation.

(The +1 of the TAB-level could also be configurable)

4. If the user wishes an optional setting, the cleaner could cut too long lines into multiple lines. (Can be combined with my point #3)

5. The Tab4-Space thing should be configurable. Before I did TABs, I used 2 spaces, not 4. (too much tabbing at the spacebar)

6. Some users (like I do) want to normalize their PHP files to [CRLF] and do not want to mix them with other [CR] (MAC) and [LF] (Linux) files in their project. I think all PHP files should have [CRLF] because then they are readable in linux and mac. Vice versa, Linux or Mac files are not readable with some Windows applications like NotePad.

So, the user should choose the output format of his new PHP file: [CRLF], [CR] or [LF].

7. There could be a recursive tool which cleanes all PHP files in a whole directory (for use at local machines where all files have temporary write-permission)

Hope it helps you to improve it! Please write me an email; maybe we can work together at it!

Regards
Daniel Marschall

Thankyou so much! you have helped me out a tonne!