Actions
User story #17825
open
We should delete property if json path is not found
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
Description
Today, if the json path configured in `JSON path` is not found, we get an error in logs alike:
SystemError(Error when trying to get path '$['badJsonPath']': No results for path: $['badJsonPath'],com.jayway.jsonpath.PathNotFoundException: No results for path: $['badJsonPath'])
This can be what we want, but perhaps we prefer to have the datasource property removed in that case. Ideally, the behavior should be configurable like what is done for behavior on a 404.
Updated by François ARMAND over 4 years ago
- Tracker changed from Bug to User story
- Priority deleted (
0)
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0-1.9 to 6.0-1.10
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 6.0-1.10 to 7.2
Updated by Alexis Mousset about 1 year ago
- Target version changed from 7.2 to Ideas
Actions