Johannes

Sure, that's no problem. However, it makes probably sense to first have a better idea of what is missing, and should be added.

You could either turn these fixes off for certain files, ``` yml # .jms.yml path_configs: migrations: paths: [app/DoctrineMigrations/*] use_statement_fixes: false ``` or, you could also set it to preserve multiple...

Yeah, let's keep this open. Different default configs depending on project type is something that could be done.

Did you manually update these files, or did you use the `generate` command?

Ah, I thought so. Unfortunately, if we do not fix the generator, your changes are lost the next time `generate` is run.

The logic is in this class: https://github.com/schmittjoh/php-stubs/blob/master/src/PHPStubs/DocumentationParser.php We should probably extract both the OO version and the function. It's probably just a matter of updating where the method/function name is...

Did you run `generate` already?

I had the urge to implement something like this myself already. However, a better solution was almost always to defer to the ACL system and let it handle the checks....

Maybe I'm missing something, but is there a problem with duplicating this information? It looks fine to me.

It is actually pretty easy to do this in an entity listener without modifying your application logic. However, I'm also open to expanding expressions. I could imagine that we add...