Christophe Coevoet

Broken compiled code for GetItemExpression on PHP 5.3

1

Assuming the `foo` variable is a container parameter, the expression `foo['bar']` will be compiled (once #110 allows to compile it) to `$context['container']->getParameter('foo_param')['bar']`. This is broken on PHP 5.3 which does...

Fixed the GetItemExpression

2

It is currently totally unusable: adding it in the expression throws a fatal error because of the missing interface, and its compilation is totally broken.

[Feature request] Allow to use an expression when compiling another expression

6

I would like to define a custom function implementing some high-level permission check for my app, which would use lower-level functions. For instance, the expression `canUpdate(object)` could then translate to...

[Feature request] Allow to define expression checks as string

2

Some bundles (FOSCommentBundle for instance) allow to configure the roles they check for different actions they are doing. But disabling the core voters make it impossible to use their implementation...

when you pass the return of a method as argument to another one, the typed code view documents the type of `$this` in the argument list instead of the type...

Wrong suggestions when addign a new repo

2

When adding a new repo on http://jmsyst.com/automated-code-reviews/repositories/new the autocompletion suggests all repos where I have write access. However, when selecting a repo where I don't have admin rights, it shows...

Add some completion for Symfony DI

3

Note sure if this should be done here, or whether the Symfony plugin should just handle them itself.

How should we implement support for project wanting to reuse Symfony providers ?

6

Currently, I'm relying on the Symfony plugin feature allowing to configure extra method references, relying on type providers defined in the plugin. This allows me to provide support for KnpMenu...

When defining the type for a property or a return type holding an ObjectProphecy, the right way to document that is `ObjectProphecy`, not `ObjectProphecy|Foo` (which would make SA tools complain...

stack trace: ``` com.intellij.openapi.project.IndexNotReadyException: Please change caller according to com.intellij.openapi.project.IndexNotReadyException documentation at com.intellij.openapi.project.IndexNotReadyException.create(IndexNotReadyException.java:67) at com.intellij.util.indexing.FileBasedIndexImpl.handleDumbMode(FileBasedIndexImpl.java:821) at com.intellij.util.indexing.FileBasedIndexImpl.ensureUpToDate(FileBasedIndexImpl.java:773) at com.intellij.psi.stubs.StubIndexImpl.getContainingIds(StubIndexImpl.java:501) at com.intellij.psi.stubs.StubIndexImpl.processElements(StubIndexImpl.java:305) at com.intellij.psi.stubs.StubIndex.getElements(StubIndex.java:100) at com.intellij.psi.stubs.StubIndex.getElements(StubIndex.java:88) at com.jetbrains.php.PhpIndexImpl.getElements(PhpIndexImpl.java:574) at com.jetbrains.php.PhpIndexImpl.getByName(PhpIndexImpl.java:992) at...