You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…numeric values.
Prior to this fix a path that contains numeric values used as position parameters would have been stripped in a way that left out the last digit. This could lead to wrong path resolution if the incorrectly constructed property name accidentally matched an existing one.
Closes: #4426
Original Pull Request: #4427
…numeric values.
Prior to this fix a path that contains numeric values used as position parameters would have been stripped in a way that left out the last digit. This could lead to wrong path resolution if the incorrectly constructed property name accidentally matched an existing one.
Closes: #4426
Original Pull Request: #4427
…numeric values.
Prior to this fix a path that contains numeric values used as position parameters would have been stripped in a way that left out the last digit. This could lead to wrong path resolution if the incorrectly constructed property name accidentally matched an existing one.
Closes: #4426
Original Pull Request: #4427
christophstrobl
changed the title
Bug: mapNestedIntegerFieldCorrectly test failed, when change the last integer to grater than 10
Update path not correctly mapped when last segment is multi digit number
Jun 28, 2023
in UpdateMapperUnitTests#mapNestedIntegerFieldCorrectly, when change the last integer to grater than 10, like this:
then add a 2rd field in EntityWithNestedMap, like this:
then, the test fails.
Expected :{"$set"={"levelOne.0.1.32"="4"}}
Actual :{"$set"={"levelOne2.0"="4"}}
The text was updated successfully, but these errors were encountered: