Autocompletion of mapped superclasses for repositories doesn't work
See original GitHub issue$this->getDoctrine()->getManager()->getRepository('MetalCountersBundle:[ctrl+space]'); // suggest only real entities, no any mappedsuperclass found
Issue Analytics
- State:
- Created 10 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Spring JPA autocompletion not working in repository class
When I start to type in repository class, there should appear autocomplete list for JPA like in the attached picture. But nothing happens....
Read more >Chapter 2. Mapping Entities - Red Hat on GitHub
You can annotate a embedded object with the @MappedSuperclass annotation to make the superclass properties persistent (see @MappedSuperclass for more ...
Read more >JPQL Query Autocompletion in IntelliJ IDEA Community | JPA ...
jpa #intellijidea #java #kotlin #jpabuddy #sqlFor the IntelliJ IDEA Community edition, JPA Buddy provides query autocompletion, as it is in ...
Read more >Auto completion doesn't work in IDEA version 2019.2 ... - GitHub
We are using the IntelliJ PSI (Program Structure Interface) to get the getters and setters for the auto completion.
Read more >Fix list for IBM WebSphere Application Server V8.5
Federated Repositories, PH42406, Support account lockout policy for the file ... PH41889, Current javamail com.ibm.ws.prereq.javamail.jar does not work with ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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)
Position ONE, the KING: Better Doctrine Refactoring. (Very Painful)
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.
@dewos prioritize your most painful issues; what you need first? 😃
my todos: