Skip to content

Parameter jsonPathExpression should not throw exception when no value found in input#9814

Merged
nielsm5 merged 1 commit intomasterfrom
issue/9768_ParamValueFromDefaultIfInputForJsonExpressionIsEmpty
Oct 23, 2025
Merged

Parameter jsonPathExpression should not throw exception when no value found in input#9814
nielsm5 merged 1 commit intomasterfrom
issue/9768_ParamValueFromDefaultIfInputForJsonExpressionIsEmpty

Conversation

@tnleeuw
Copy link
Contributor

@tnleeuw tnleeuw commented Oct 23, 2025

Changes

JSON Path expressions on parameters should not throw an exception when the message is empty, or the path is not found in the input.
Instead, the parameter default value should be used.

Issues

Backports

@tnleeuw tnleeuw requested review from evandongen and nielsm5 October 23, 2025 08:49
@tnleeuw tnleeuw self-assigned this Oct 23, 2025
@tnleeuw tnleeuw changed the title Parameter jsonPathExpression should not throw exception when no value found in input (#9812) Parameter jsonPathExpression should not throw exception when no value found in input Oct 23, 2025
@sonarqubecloud
Copy link

@nielsm5 nielsm5 merged commit 94ba955 into master Oct 23, 2025
30 checks passed
@nielsm5 nielsm5 deleted the issue/9768_ParamValueFromDefaultIfInputForJsonExpressionIsEmpty branch October 23, 2025 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jsonPathExpression attribute on Param breaks when set via property

2 participants