GDSL Awesomeness – Adding Hinting for missingMethod implementation

24 / Sep / 2012 by Kushal Likhi 0 comments

hi,

 

Suppose we have used method missing in our code and we want to give syntax-hinting for these methods then we can go as follows:

 

Suppose we have this class which implements method missing:
[java]
class Pixel {
def Top
def Left
def Color
def methodMissing(String name, args) {
// implementation of dynamic method synthesis, it will intercept methods in signature increment<propertyName>(Integer step)
}
}
[/java]

 

Now GDSL Script for the above class will be like:
[java]
def ctx = context(ctype: "my.package.Pixel")
contributor (ctx) {
// Add generic methods
classType?.fields?.each {
method(name: "increment${it.name}", params: [step: Integer], type: ‘int’)
}
}
[/java]
The above script will give autoCompletes for these dynamic methods.

 

Read Further in the “GDSL AWESOMENESS” Series

  1. GDSL Awesomeness – Introduction to GDSL in IntelliJ Idea
  2. GDSL Awesomeness – Understanding Context And Contributors in Detail
  3. GDSL Awesomeness – Defining dynamic property in a class
  4. GDSL Awesomeness – Defining dynamic method in a class
  5. GDSL Awesomeness – Adding Hinting for missingMethod implementation
  6. GDSL Awesomeness – Setting a global context
  7. GDSL Awesomeness – Delegating Closure Calls
  8. GDSL Awesomeness – Defining methods in a closure passed to method of particular name
  9. GDSL Awesomeness – Defining Properties in a closure passed to method of particular name
  10. GDSL Awesomeness – Contributing to classes which match a path/name pattern
  11. GDSL Awesomeness – contributing methods with current class return types or parameters
  12. GDSL Awesomeness – AutoComplete Script for grails-Mail-Plugin “sendMail” closure
  13. GDSL Awesomeness – Getting Code of a method or Field in GDSL Script
  14. GDSL Awesomeness – Advanced Example showing domain properties implementation

 

 

Hope It Helped.
Kushal Likhi

FOUND THIS USEFUL? SHARE IT

Leave a Reply

Your email address will not be published. Required fields are marked *