Add support for constraints on nested fields.

[thowimmer]

Hi all,

I added support for constraints on nested fields.
The support has been implemented by simply choosing the last JSON path element as the bean property name:
someNestedObject.someField -> someField = bean property name
someField -> someField = bean property name

[coveralls]

Coverage increased (+0.004%) to 92.011% when pulling 2dee63d on thowimmer:nested-constraints into 9138472 on ePages-de:master.

[ozscheyge]

Hey @thowimmer ,

thank you for the contribution!

As far as I can see, this was already possible before using the withMappedPath method in an explicit fashion, e.g.

withMappedPath("pathTo.my.nestedPropertyWithConstraints", "nestedPropertyWithConstraints")

This is how we are using it so far. Your change certainly makes this more convenient!
However, I'm uncertain whether there could be cases, where this behavior isn't desired

[ozscheyge]

Reading the docs of substringAfter https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.text/substring-after.html your implementation would only work for one nesting level:

path --> beanPropertyName
---

one.level --> level
two.levels.areTooMany --> levels.areTooMany

[thowimmer]

Hi @ozscheyge,

As far as I can see, this was already possible before using the withMappedPath method in an explicit fashion, e.g.

Yes I actually saw that. I was not sure whether the visibility of the other methods is itentional. But I guess that's the case after having this conversation:-)

This is how we are using it so far. Your change certainly makes this more convenient!
However, I'm uncertain whether there could be cases, where this behavior isn't desired

I totally agree. I was expecting this method to behave like I implemented it in this PR. However - you judge whether this is what you want or not. I'm also fine to use your proposed solution with the withMappedPath method.

Reading the docs of substringAfter your implementation would only work for one nesting level

Yes good catch ! Thanks :-) I will refactor it to substringAfterLast.

I leave it up to you whether you'd like this feature to be merged or not :-)

[ozscheyge]

I'd leave it open for further feedback/opinions. If there are no objections, it should be integrated!

[mduesterhoeft]

Thanks for the contribution. LGTM