Problem

The JsonPathService::extractFirst method was not returning the correct value when extracting data using JSON path expressions, causing data flow issues between nodes.

Root Cause

The method was wrapping results in an additional array layer instead of returning the direct result.

Solution

Refactored the extractFirst method to handle results directly without additional wrapping, ensuring the correct value is returned.

Impact

  • JSON path extractions now return expected values
  • Data transformations work correctly
  • Node processors receive properly formatted input data

Comments

joevagyok created an issue. See original summary.

gxleano’s picture

I have contributed (not only by code, but discussion, presentation, testing or anything related).

d34dman’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.