Autocompletion of mapped superclasses for repositories doesn't work

[Koc]

$this->getDoctrine()->getManager()->getRepository('MetalCountersBundle:[ctrl+space]'); // suggest only real entities, no any mappedsuperclass found

http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/inheritance-mapping.html#mapped-superclasses

[Haehnchen]

so this one is not visible?

getRepository('Bundle:EntitySubClass')

[Koc]

Entity sublcasses are visible, mapped superclass is not visible.

[tiger-seo]

+1 here
$repo = $this->getDoctrine()->getManager()->getRepository(Twitter::class);
and $repo is Doctrine\Common\Persistence\ObjectRepository
but if $repo = $this->getDoctrine()->getManager()->getRepository(BaseTwitter::class);
then $repo is MyProject\MyBundle\Repository\TwitterRepository

class signature:
class Twitter extends BaseTwitter

mapping:

MyProject\MyBundle\Entity\BaseTwitter:
    type: mappedSuperclass
    repositoryClass: MyProject\MyBundle\Repository\TwitterRepository

[Haehnchen]

ref/dup #346

[Koc]

/**
 * @ORM\MappedSuperclass(repositoryClass="Metal\NewsletterBundle\Repository\SubscriptionCategoryRepository")
 */
abstract class SubscriptionCategory

Also value for repositoryClass isn't autosuggested and not clickable

[cmfcmf]

👍 Having the exact same problems with my entities.

[dewos]

@Haehnchen I don't want to rush things but, since some years have passed, any update about this one? At work we use MappedSuperclass and Embedded everywhere, nowdays :)

[Haehnchen]

@dewos prioritize your most painful issues; what you need first? :)

my todos:

• metadata support completion / navigation (yaml, xml, annotations [API] Provide an index with annotated elements stubs idea-php-annotation-plugin#53)
• "mappedSuperclass" need to be indexed on metadata value
• Doctrine Refactoring to support new index
• Type provider for getRepository Implement PhpTypeProvider3 for type resolving #792

[dewos]

hahhah @Haehnchen, ok then, here we come the "Top 3 most painful Issues 2016 at work (real life)". Warning, dragon ahead! :)

Position THREE: Better Twig autocomplete. (Would be nice)
[Twig] No autocomplete in nested for-loop #576

Position TWO: Better doctrine QB autocomplete. (Painful)

1. In some cases Object::class notation does not work at all. For example for custom joins like $qb->join(Object::class, 'g', 'WITH', 'u.status = ?1'), or ->from(Object::class, 'g')
2. Embeddable [Doctrine] Add completion for "Embeddables" of 2.5 #471

Position ONE, the KING: Better Doctrine Refactoring. (Very Painful)

1. Refactoring a class name doesn't change the @ ManyToOne("targetEntity=xxx") (and similar) in Doctrine mapping annotations.
2. Refactoring a mapped field in entity doesn't change the field name referenced in the query builder.

Honorable mention:
No static inspection\warning on "not imported (use)" annotation with "AS" (like @Assert\FooBarNotHere).

Anyway, without your plugin everything would be much worse, so... no pressure here 👍
@Haehnchen I'm also a Java dev, I hope to find some time sooner or later for learning the IDEA ecosystem and help you out.