Ryan-Nightwish opened a new pull request, #808:
URL: https://github.com/apache/flink-agents/pull/808

   <!--
   * Thank you very much for contributing to Flink Agents.
   * Please add the relevant components in the PR title. E.g., [api], 
[runtime], [java], [python], [hotfix], etc.
   -->
   
   <!-- Please link the PR to the relevant issue(s). Hotfix doesn't need this. 
-->
   Linked issue: #803 
   
   ### Purpose of change
   
   Two doc-quality fixes for 
`docs/content/docs/get-started/quickstart/workflow_agent.md`:
   
   1. **Python `process_input` code snippet out of sync with source** (line 
134-135) — the doc showed `input_event = InputEvent.from_event(event)` followed 
by `input: ProductReview = input_event.input`, but the actual source 
(`review_analysis_agent.py` line 91) uses `input = 
ProductReview.model_validate(InputEvent.from_event(event).input)`. Updated the 
doc to match the source.
   
   2. **Comment wrongly mentions `ProductSuggestionAgent`** (line 51-52) — the 
"Prepare Agents Execution Environment" snippet's comment said the connection is 
"used by the ReviewAnalysisAgent **and ProductSuggestionAgent**", but the 
section introduces the single-agent example. Removed the 
`ProductSuggestionAgent` reference to match the actual single-agent source.
   
   ### Tests
   
   - Verified the updated code snippet matches `review_analysis_agent.py` line 
91
   - Verified the updated comment matches the single-agent source comment
   - No code changes
   
   ### API
   
   No public API changes.
   
   ### Documentation
   
   <!-- Do not remove this section. Check the proper box only. -->
   
   - [ ] `doc-needed` <!-- Your PR changes impact docs -->
   - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [x] `doc-included` <!-- Your PR already contains the necessary 
documentation updates -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to