-
Notifications
You must be signed in to change notification settings - Fork 737
Regression in beneathPath in 2.0.3 #573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the report. I suspect this is an unintended side-effect of the fix for #473. Does it work with |
Yes, workaround worked for that case but didn't work for more complicated one with optional field present in one subsection, but not in the another: {
"order": {
"routeNodes": [
{
"address": "Lennarts Väg 3,Arfors,SE",
"position": {
"latitude": -4.196291170128276,
"longitude": 117.72075222004281
},
"time": "2019-01-14T21:11"
},
{
"address": "Karls Gata 842,Arborg,SE",
"position": {
"latitude": -42.12475432500546,
"longitude": -22.791496608870403
}
}
]
}
} responseFields(
beneathPath("order.routeNodes.[]"),
fieldWithPath("address").description("Address").type(JsonFieldType.STRING),
subsectionWithPath("position")
.optional()
.description("Optional <<get-order-details-2-route-position,position>>")
.type(JsonFieldType.OBJECT),
fieldWithPath("time")
.optional()
.description(
"Optional time in format `yyyy-MM-dd'T'HH:mm`. Field will be always set on the first node")
.type(JsonFieldType.STRING)), Then I get:
|
@wilkinsona do you want me provide anything else? |
Thanks for the offer. I think I have everything from you that I need. I just need to find the time to look at what the necessary fix should be. |
Seems like there was some change in how
beneathPath
works in 2.0.3The following worked in 2.0.2:
where document was(test data no personal info)
But starting from 2.0.3 I get this error message:
The text was updated successfully, but these errors were encountered: