We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We're not able to parse float value found in JSON
Here's the content
{ "id": 8385455, "title": "BANDE FROID KOOLPAK", "currency": "EUR", "price_type": "RECOMMENDED", "sales_price": 23.0, "sales_price_ht": 19.166666666666668, "sales_loss": 3.25, "prmp": 2.55, "cession_price": 2.708, "start_date": "2021-07-19T12:07:44+02:00", "stop_date": "2021-07-28T12:07:44+02:00", "margin_stock": { "value": 16.616666666666667, "rate": 72.2463768115942 }, "margin_expected": { "value": 16.458666666666666, "rate": 71.55942028985507 }, "quantities_for_equals_turnover": { "value": 0.0, "rate": 0.0 }, "quantities_for_equals_margin": { "value": 0.0, "rate": 0.0 }, "are_all_item_same_price": true, "taxe_rate": 20.0 }
The jsonpath is tested and works correctly
It works fine with text and integer.
It might be related to this commit: 47e28a5
Cerberus version: 4.12-RELEASE
The text was updated successfully, but these errors were encountered:
483b9aa
This issue is resolved but needs to be covered in the regression tests campaign. I couldn't find any float field in the API used in this test case.
Sorry, something went wrong.
e957a8a
Same issue with JSON Object, fix in the previous commit Both issues now tested in https://prod.cerberus-testing.com/TestCaseScript.jsp?test=ENGINE%20:%20Property&testcase=0007A&step=2&tabactive=tabSteps (was not tested before)
No branches or pull requests
We're not able to parse float value found in JSON
Here's the content
The jsonpath is tested and works correctly
It works fine with text and integer.
It might be related to this commit: 47e28a5
Cerberus version: 4.12-RELEASE
The text was updated successfully, but these errors were encountered: