Instead of removing this FIXME ... what if we:

• Remove this recipe entirely
• Deprecate the package

I created this package because log files were a mess for me ... but recently PhpStorm added syntax highlighting and other improvements to logs ... so I no longer need this package. What do you think?

Works for me, recipe is now removed.

Here is the sidekick PR to merge+tag: symfony/debug-pack#11

Could you please elaborate why this is removed?

@javiereguiluz could you share with us the way you're going through logs with PhpStorm? It looks very interesting :-) 🙏

@B-Galati the best of all is that I don't do anything special :) What I tried to say in my previous comment is that in the past, PhpStorm showed logs as an endless stream of black & white text. I couldn't find anything there.

But in recent versions, logs are shown like this (by default, no plugins installed):

For me this is more than enough. The highlighting makes everything very easy to find. I know that the Monolog handler that we removed is a bit better sometimes because it formats some information in several lines, etc. But 95% of the times, PhpStorm is enough for me. That's why I suggested removing this.

Thanks @javiereguiluz, super interesting 👍

(It was not working for me because I had Ideolog plugin enabled)

I configured Ideolog and it's also giving me something easier to read FYI:

For projects started before this release and using the EasyLogHandler from the official symfony/debug-pack, this will actually break the dev build after running composer update , as the easycorp/easy-log-handler package will be removed but not the config file added by the original recipe (which references the EasyCorp\EasyLog\EasyLogHandler service).

I am also using the latest PhpStorm 2020.1 but I have no syntax highlighting on the logs, with our without Ideolog.

@cristi-contiu I'm using PhpStorm 2019.3 and I haven't installed any plugin related to logs. In fact, I only have 4 custom plugins, so that's why I think this must be some built-in behavior:

@javiereguiluz Thank you very much for your reply! In case anyone else has the same issue, watch out for File Types associated to the .log extension. In my case, the .log files were associated with the "ANSI Aware" file type the from the "ANSI Highlighter" plugin. Removing the association from PHPStorm Settings > Editor > File Types > ANSI Aware or uninstalling the plugin did the trick.

Before (notice the .dev.log file icon vs the .env icon):

After:

PHPStorm 2020.1, removed association of *.log for ANSI Aware plugin, still can't see behaviour you are describing

@ostrolucky Do you see the color scheme on the .env file?

@cristi-contiu WDYM? If I have some sort of syntax highlighting in .env file? No, I don't

@ostrolucky My bad, I thought that the .env files color scheme was the same as the .log files. It turns out the .env file color scheme was given by a PHPStorm plugin.

As a test, I disabled all downloaded plugins and still got syntax highlighting for .log files (but not in .env files). I left all bundled plugins enabled.

In my case, the .log files are identified as Text file type (using the *.log pattern), but even if I remove the association, I still get highlighting. My color scheme is Darcula (but the highlighting also work with Classic Light and other themes).

@ostrolucky you might have Ideolog plugin installed. Interestingly, it will not detect the log format here, if I uninstall it, it starts working for me.

Fresh PC and installation, here is how it looks first time opening these log files for me:

Installing either of these plugins doesn't help. I really don't know how this works for everybody else out of the box :(