Daniel Espendiller

yes, in general i am thinking to support "wildcards" for templates in many places and also to improve all php completion with code path analyse, with both this would catch...

yes, noticed it also a long time ago; resulted because of api / lexer changes on twig plugin

@theredled yes this mentioned method check is for performance and also to not overflow the phpstorm signatures for every method. By removing this simply we are saying we are responsible...

yes, its really annoying sometimes, plugin knows must cases, i will try to find if there is any extension point to hide this external warning

Thanks for this list, just for related issues there is also one on PhpStorm itself to provide an API for this: https://youtrack.jetbrains.com/issue/WI-47938 Maxim Kolmakov commented 2 Aug 2019 13:13 >...

> Matouš Němec commented 8 Jan 2022 20:39 > > Hello, solution is extension point implicitUsageProvider. You can implement com.intellij.codeInsight.daemon.ImplicitUsageProvider to your plugin to solve this problem. Use method isImplicitUsage....

thanks for this PR, will also comeback here, fixing lost features for API changes ;)

@stof any example?

can you provide more context here, where you define `$this->container`? from the naming/screenshot: guessing that you use this pattern inside a test case, so its maybe inside a `setUp`?

that looks like a missing merge, where `website` "set" should extend with the type. understanding that is not easy. **first starting point for {{ web }}** https://github.com/Haehnchen/idea-php-symfony2-plugin/blob/master/src/main/java/fr/adrienbrault/idea/symfony2plugin/templating/util/TwigUtil.java#L639 this is extracting...