Nested Properties

[lviggiano]

It could be interesting to think about some structure (i.e. nesting)

interface Foo extends Config {

    String fooProp();

    interface Bar extends Config {
        barProp();
    }

    @Key("bar");
    Bar bar();
}

So, to access barProp, the default key in the properties file would be foo.bar.barProp.
Method invocation will then be Foo.bar().barProp().

Not sure it is a good thing to have. Implementation may not be trivial. We can discuss it.

[eladidan]

Any special reason this branch is not merged? This seems like such a huge improvement on the API. Can I help in any way (I really love this project btw...)?

[lviggiano]

No special reason: need to understand and consider how this thing should work, and I was not fully convinced by the implementation

[eladidan]

It's a great feature. One that would help take this library from great to
greater.
Can't comment about the implementation. I just briefly looked at the diff
with master and saw that it has changed dramatically since the time of the
branch.

/Idan
On Oct 16, 2014 5:28 PM, "Luigi R. Viggiano" [email protected]
wrote:

No special reason: need to understand and consider how this thing should
work, and I was not fully convinced by the implementation

—
Reply to this email directly or view it on GitHub
#2 (comment).