How to Tackle Common Groovy Pitfalls in IntelliJ IDEA

IDE Errors

When writing Groovy scripts in IntelliJ IDEA, the IDE frequently highlights code in red or reports errors even though the script runs correctly, and sometimes it fails to warn about runtime problems. This is mainly due to the IDE's incomplete support for Groovy's extensive language features.

Accessing Object Properties

Groovy provides three syntaxes to retrieve a property from an object such as user:

user.name
user["name"]
user.getName()

The first and third forms have different semantics because Groovy does not normally provide a getName() method; the bracket notation is a special Groovy syntax. All three forms work not only for custom User objects but also for JSON objects, which is why they are often used together with JsonPath.

Generic Method Invocation

A generic base class ThreadBase<T> was created to hold a thread‑local data object:

static class TT extends ThreadLimitTimesCount {
    Mirro m
    int aid = 0
    public TT(Mirro mirro, int times) {
        super()
        this.m = mirro
        this.times = times
    }
    @Override
    protected void doing() throws Exception {
        def pre = m.createPre()
        if (aid == 0) {
            aid = pre.getJSONObject("data").getIntValue("activity_id")
        }
        m.delPre(aid)
    }
}

An earlier version omitted the m field and used t instead, which caused a runtime error after the Mirro property was removed.

The it Keyword

In Groovy, the implicit it variable is handy for iterating over collections. For example:

5.times { output(it) }

When nesting loops, the same it identifier can be used for both outer and inner iterations without conflict:

3.times {
    output(it * 10)
    3.upto(5) { output(it) }
}

The console output confirms that the outer it (multiplied by 10) and the inner it (the inner loop index) are distinct, demonstrating the robustness of Groovy's design.