I wonder if this module will allow me to build a command/sub-command hierarchy, with following convention:
- A sub-command is itself a command
- Support any level of sub-command nesting
Example:
person: {
"name": "Joe",
"address": {
"street": "a-street",
"city": "a-city"
}
}
Considering above data-structure, I want to render commands dynamically....
- Create a Person.groovy that only exposes commands "name" and "address"
- When the user presses 'tab' after 'address', schema for 'address' is shown.
- Note that the schema could be further nested. I kept it simple for the sake of this example.
I guess, the dynamic nature of groovy can come handy to do this. Does this sound a reasonable thing to allow in the core ?
I wonder if this module will allow me to build a command/sub-command hierarchy, with following convention:
Example:
person: {
"name": "Joe",
"address": {
"street": "a-street",
"city": "a-city"
}
}
Considering above data-structure, I want to render commands dynamically....
I guess, the dynamic nature of groovy can come handy to do this. Does this sound a reasonable thing to allow in the core ?