If the file has a large error report (circa 1500 errors), the report gets truncated and does not display all

[gabriel403]

As in this screenshot, it only shows for the first ~1k lines of code

[benmatselby]

Currently unable to replicate this. I've just executed on a file which is 1866 lines long and the linter, phpcs and phpmd all showed errors on line 1865.

I assume you have run the command from the console window in the terminal and it is reporting errors?

[gabriel403]

@benmatselby no just the plugin atm, don't know if it's the setup?

[gabriel403]

What would the command be to run it from cli?

[benmatselby]

From inside of Atom, either do cmd+alt+i or "View -> Developer -> Toggle Developer Tools" and then click on the "Console" tab

This will then output the exact command that this plugin is running. Take that command and put it in your terminal and compare the results.

[gabriel403]

[benmatselby]

OK, so wonder if it is the sheer amount of errors, rather than lines. How many errors do you have?

[gabriel403]

Heh

"totals":{"errors":3106,"warnings":68}

[gabriel403]

Lemme prune the file down and see if I can find the magic error number

[benmatselby]

Install php-cs-fixer and hook that into the plugin then you can do cmd+k, cmd+f to run the fixer on the current file

[benmatselby]

Updated title to reflect issue

[gabriel403]

"totals":{"errors":1151,"warnings":40} anymore than that is what causes the gutter to not fully display errors

[benmatselby]

It is about the data we get back from child_process in stdout

[benmatselby]

Closing this issue down, as it's been nearly a decade, and I'm going to archive the repo.