The type checking DSL provides several helper methods to get access to the arguments. See for example:

In your case you're probably looking for something like :

Where you want a Map, but in any case, since you need to check the keys, it has to be *more* than a Map, it has to be a Map literal (hence why you see MapEntryExpression). So you should check the structure of the ArgumentListExpression explicitly. If we can get the macro stuff merged into 2.5, there will be experimental support for matches, that would make it even easier, but we're not there yet.

2015-08-19 15:27 GMT+02:00 Anto Aravinth <>:

I'm writing an type checker for an DSL. So the type checker looks like this:


class MyAppDSLTypeChecker extends GroovyTypeCheckingExtensionSupport.TypeCheckingDSL {



    Object run() {

        methodNotFound { receiver, name, argList, argTypes, call ->

            println argList

            handled = true





When my DSL runs, for now it just prints argList, which is something like this:


org.codehaus.groovy.ast.expr.ArgumentListExpression@1fc8bb61[org.codehaus.groovy.ast.expr.NamedArgumentListExpression@3385ed94[org.codehaus.groovy.ast.expr.MapEntryExpression@1db0a9f9(key: ConstantExpression[asdasdasddsasd], value: ConstantExpression[someId])]]


Is there any Visitor support does Groovy gives out of the box, so that I can traverse the above ArgumentListExpression AST node? So this is my idea, if method name matches my DSL rule, and I need to check its param, which should be only map. And that map also should be of some keys. So need to check them.


Thanks for your input.