This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 225731 - Code completion should continue to work on further methods in a chain
Summary: Code completion should continue to work on further methods in a chain
Status: RESOLVED DUPLICATE of bug 152778
Alias: None
Product: groovy
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: Martin Janicek
URL:
Keywords:
: 228764 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-02-05 00:09 UTC by eddelplus
Modified: 2013-06-26 13:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description eddelplus 2013-02-05 00:09:10 UTC 
When editing code like this

def eng = new GroovyScriptEngine()
eng.getConfig().

the code completion works great after eng and the period (correctly implying that eng is class GroovyScriptEngine).

It should also continue to work after .getConfig(), a method that clearly results in a CompilerConfiguration object, but it never does in any method chains.

That's also the case for Groovy intrisic stuff, e.g. a simple chain like

def xy = "foobar"
xy.padLeft(12). --> again to code completion

This is so substantially annoying, I'll file it as DEFECT, not ENHANCEMENT
Comment 1 Martin Janicek 2013-02-05 08:56:01 UTC 
Hi, thanks for the report. This is a type interference problem (duplicate of the issue 152778). I'm aware of this and will try to fix it as soon as possible, but don't want to promise anything
Comment 2 Martin Janicek 2013-04-22 07:39:38 UTC 
*** Bug 228764 has been marked as a duplicate of this bug. ***
Comment 3 Martin Janicek 2013-04-25 14:48:49 UTC 
First sketch of the possible solution done in: web-main #2553ab6b0c22

The code completion works on method chain but only in cases when the "base" variable is directly declared (statically typed). I need to spend more time on this to get it working also for dynamic variables.
Comment 4 Martin Janicek 2013-06-26 13:20:15 UTC 

*** This bug has been marked as a duplicate of bug 152778 ***