amend pipe_input example in docstring

[sT0v]

Documentation example discontinuity fixed for pipe_input.
The example would have failed if executed.

Changes

fixed the docstring example

How I tested this

I did not test this

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 24e5872 in 26 seconds

More details

• Looked at 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. hamilton/function_modifiers/macros.py:848

• Draft comment:
  The change in the docstring example is correct. The function now returns the sum of p1, p2, and p3, which aligns with the function signature and expected behavior.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The change in the docstring example is correct and aligns with the intended functionality of the pipe_input decorator. The example now correctly returns the sum of p1, p2, and p3, which is consistent with the function signature and the expected behavior of the pipe_input decorator.

2. hamilton/function_modifiers/macros.py:850

• Draft comment:
  Consider adding this example to the Sphinx documentation under docs/ to illustrate the use of pipe_input with multiple parameter targets.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The code is a documentation update, but it includes a code example that should be added to the Sphinx documentation.

Workflow ID: wflow_jXXxtyK78spo6yFF

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[elijahbenizzy]

Thanks!