Autocompletion does not work with enum ctors
See original GitHub issueThe title explains it all. You can’t use intellisense in enums’ ctors:
public enum ExampleEnum {
ValueOne("You can't use intellisense in here") // <------
;
ExampleEnum(String string) {
}
}
Environment
- Operating System: Arch Linux
- JDK version: 1.8.0_162
- Visual Studio Code version: 1.20.1
- Java extension version: 0.20.0
Steps To Reproduce
- Create an enum
- Try typing a few words and pressing ctrl + space to bring intellisense
Current Result
You don’t get any autocompletion
Expected Result
Intellisense should work normally
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Autocomplete not working for enum -Swift 3 - Stack Overflow
1 Answer 1 ... Since your enum variable language is optional, so it wont autocomplete.Generally autocomplete works with . prefix if the variable ......
Read more >Intellisense does not autocomplete Enum type names
In VS if a method accepted an enum parameter, I could get away with only typing the enum value into intellisense (I did...
Read more >Using a Custom Enum To Get Tab-Completion on a Parameter
PowerShell has a data type called an enum, which is a way to set a variable for a number of predefined constants.
Read more >Typescript Enums are bad!!1!!!1!!one - Are they really?
For me StringEnums work perfectly, allow clean, readable, organised list of values and you can benefit from autocomplete features from your IDE, ...
Read more >[UE 5.1] VisualStudio 2022 Intellisense for engine files not ...
EDIT: It also appears to mostly only affect Actor files. My function library and static enum classes seem to work completely fine in...
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 was fixed upstream today: https://bugs.eclipse.org/bugs/show_bug.cgi?id=532366#c16
It might take a few weeks before we can consume those bits.
Looks like the fix has finally made it into eclipse.jdt.ls with the recent updates to the target platform! I can no longer reproduce the bug after trying eclipse/eclipse.jdt.ls@5483c3a, so I think this issue can be closed now.