Java Model Decorators (beta)

[RicoYao]

Adds the ability to pass in an accompanying decorations file for:

• Extending a class
• Implementing interfaces
• Adding annotations to the class, property variables, property getters, other methods
• Specifying additional imports

Example usage:
plank --lang=java --java_decorations_beta=decorations.json my_model.json

decorations.json:

{
    "class": {
        "extends": "BaseModel",
        "implements": ["ModelInterface"],
        "annotations": ["CustomAnnotation"]
    },
    "constructor" : {
        "annotations": ["CustomAnnotation"]
    },
    "properties": {
        "my_property": {
            "variable": {
                "annotations": ["CustomAnnotation"]
            },
            "getter": {
                "annotations": ["CustomAnnotation"]
            }
        }
    },
    "methods": {
        "mergeFrom": {
            "annotations": ["CustomAnnotation"]
        }
    },
    "imports": [
        "com.test.package.BaseModel",
        "com.test.package.ModelInterface",
        "com.test.package.CustomAnnotation"
    ]
}

[rahul-malik]

@RicoYao - Why would we do extension in the decorators file vs the schema? We have support for extends which I assume would be sufficient here

[RicoYao]

@RicoYao - Why would we do extension in the decorators file vs the schema? We have support for extends which I assume would be sufficient here

@rahul-malik Perhaps I misunderstood our last discussion, but I believe extends in the schema is meant to be used for inheriting properties, but not to actually define class extension. That was a design decision that predates my involvement, but I agree with it FWIW, as we don't want to encourage class extension.

[RicoYao]

I had fixed this in a local branch, and didn't realized I hadn't pushed it any PRs. I can split out into a separate PR if we prefer.