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

JsonPath array result type #327

christophd opened this Issue Jan 15, 2018 · 0 comments


None yet
1 participant

christophd commented Jan 15, 2018

When using a JsonPath validation expressions like $ should result in an JSONArray of id element values. Instead the resulting array is automatically converted into a Json string value (e.g. "[1,2,3,4,5]")

The Json string value does not apply for collection based assertion matchers (e.g. Hamcrest). Matchers such as hasItem(), hasItemInArray() will fail as the Json path result is not of type array anymore.

@christophd christophd added this to the v2.7.4 milestone Jan 15, 2018

christophd added a commit that referenced this issue Mar 12, 2018

@christophd christophd removed the READY label Mar 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment