Tobias Minich

I didn't want to put more work on your shoulders over the weekend as you have already been incredibly helpful today, but there are a few things not quit working...

Since I'm about to leave work I'll leave it here for now: This works: ```php /** * @param array $specs Specifications for parsing. * * @psalm-param array{ * allowed: list,...

Thanks a lot. PSALM syntax, thanks to being able to use @psalm-X tags, currently seems to be the best way to get deep-assoc-completion hints without PHPStorm showing them weirdly and/or...

Thanks a lot. For me that's enough, I just didn't want deep-assoc-completion's parsing break on valid PSALM syntax.

I've started to work on this but ran into some issues, it's not as simple as just changing the method itself. Before I continue I would appreciate some input on...

Well, for me personally the data itself doesn't really matter, I'd just like a 'something there' instead of 'null' =)

I had a similar need. I solved it with a custom Psy-Shell command: ```php use Psy\Command\ReflectingCommand; use Psy\VarDumper\Presenter; use Psy\VarDumper\PresenterAware; use Symfony\Component\Console\Input\InputInterface; use Symfony\Component\Console\Output\OutputInterface; class MonitorDb extends ReflectingCommand implements PresenterAware...

It's technically not ignored, the exception is thrown before the actual command code with all it's scaffolding (including parsing of the command line options) is run, so verbosity level is...

Configuration option 'always_verbose' maybe?

Just noticed, trace rendering doesn't work at all if the log originates from a XHttpRequest.