Related Issues

• fixes Results of intermediate PromptNodes in a Multi-PromptNode-Pipelines are burried #3878

Proposed Changes:

As noted by the author of #3878 the results of intermediate PromptNode(s) in the pipeline are stored under the invocation_context results variable thus making them a bit less accessible than having it ideally as they key under the root of the resulting dictionary returned to the Haystack pipeline user.

The change required is relatively simple. We elevate output_variable value under the root output dictionary returned to the Haystack pipeline user. However, we also leave it in invocation_context so other nodes down the pipeline can use it.

How did you test it?

No new tests were added but the existing tests have been adjusted to check for presence of output_variable in the resulting dictionary. We also check the value of that variable for validity.

Notes for the reviewer

There is some duplication of keys and values in the resulting dictionary. The reason for that is that we need to put key/value resulting pair in the invocation_context as well. We'll remove the duplication once we refactor pipelines inner logic and clean up pipeline run signatures.

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added tests that demonstrate the correct behavior of the change
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
• I documented my code
• I ran pre-commit hooks and fixed any issue