User story #17825: We should delete property if json path is not found - Datasources - Issue Tracker

Actions

Copy link

User story #17825

open

We should delete property if json path is not found

Added by François ARMAND almost 4 years ago. Updated 6 months ago.

Status:

New

Priority:

N/A

Assignee:

Target version:

Rudder plugins - Ideas

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.