You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For types that implement java.util.Map, Groovy offers specialized support for property access. Instance fields can only be referenced using the attribute operator (.@). Instance methods can be referenced through a call expression or method pointer/reference operator (.& or ::). Property access through the dot operators (. and .? and probably .*) creates references to map entries instead of fields, properties or methods. And the call operator (()) can also be used to retrieve a value and "call" the result.
Current IDE support for these many variations, including references inside closures that do not have explicit object expressions is a mixed bag (see below).
The text was updated successfully, but these errors were encountered:
- disable code hover/select for map key
- highlight property expression as MAP_KEY
- propose only fields for "map.@x"
- propose only methods for "map.&x" or "map::x"
- propose only methods for "map.x" (no Java-bean variants)
- change inferred type of getAt(Object,String) extension method
#1143
- disable code hover/select for map key
- highlight property expression as MAP_KEY
- propose only fields for "map.@x"
- propose only methods for "map.&x" or "map::x"
- propose only methods for "map.x" (no Java-bean variants)
- change inferred type of getAt(Object,String) extension method
#1143
For types that implement
java.util.Map
, Groovy offers specialized support for property access. Instance fields can only be referenced using the attribute operator (.@
). Instance methods can be referenced through a call expression or method pointer/reference operator (.&
or::
). Property access through the dot operators (.
and.?
and probably.*
) creates references to map entries instead of fields, properties or methods. And the call operator (()
) can also be used to retrieve a value and "call" the result.Current IDE support for these many variations, including references inside closures that do not have explicit object expressions is a mixed bag (see below).
The text was updated successfully, but these errors were encountered: