Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Symbols from transient dependencies are not included in code completion
See original GitHub issueIt is better if there is auto completion for annotations such as @required
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
[bug] Bazel generator does not put transitive dependencies in ...
When using Conan with Bazel the generated BUILD files do not include any of the dependency's transitive dependencies in the included deps ...
Read more >Intellij can't resolve transitive dependencies - Stack Overflow
version=1 or jenkins build is going through fine but intellij is all red and angry when i open the modules in IDE, this...
Read more >Announcing NuGet 6.3 - Transitive Dependencies, Floating ...
View transitive dependencies in Visual Studio. ... While the work is completed in the 6.3 release, you will likely not see any benefit...
Read more >Understanding dependency resolution - Gradle User Manual
This chapter covers the way dependency resolution works inside Gradle. ... If no ranges are involved, then the highest version that is not...
Read more >Introduction to the Dependency Mechanism - Apache Maven
With transitive dependencies, the graph of included libraries can ... (src/test/java) but not in the model code (src/main/java). system
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
It’s by design that annotations from packages not listed in
dependenciesdon’t show up.Automatically adding the package to
pubspec.yamlwould be an option, but really that would mean listing all symbols from transient dependencies in the code completion and I generally think that would be a bad idea (the list is already very long with just symbols from direct dependencies). Hope this makes sense!Yes, as you said, it’s because of meta package dependency. If you don’t see much deal on feature request, this can be closed now