groovy / groovy/groovy-eclipse
Difficulty to write decimal numbers with code assist auto-activation enabled
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 681
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Suppose you have code assist auto-activation enabled and you want to type:
def a = 12.0
def b = 5.0
When you've finished to type def a = 12.0 and hit Enter to go to the next line, now Greclipse replaces your input with: def a = 12.toUnsignedString0(arg0, arg1).
It's very annoying. I understand why it happens (I think it's due to #687), but I think that some kind of solution should be found. Maybe in this special case, the suggestion list could also suggest simple digits (from 0 to 9), with the digit you typed on top... Or simply disable auto-activation (even when enabled) for numbers...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Eclipse with Groovy code-assist auto-activation enabled by entering the decimal examples and pressing Enter. Review the behavior discussed in #687; done means decimal input such as 12.0 and 5.0 is not replaced by an auto-completion expansion while auto-activation remains enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100