rosemarYuan opened a new issue, #797:
URL: https://github.com/apache/flink-agents/issues/797

   ### Search before asking
   
   - [x] I searched in the 
[issues](https://github.com/apache/flink-agents/issues) and found nothing 
similar.
   
   ### Description
   
   ### Search before asking
   
   - [x] I searched in the 
[issues](https://github.com/apache/flink-agents/issues) and found nothing 
similar.
   
   ### Description
   
   The YAML Agent quickstart doc 
(`docs/content/docs/get-started/quickstart/yaml_agent.md`) shows bare 
`copyResource(...)` calls in the "Load and Run" Java code block, but the actual 
code in `YamlWorkflowAgentExample.java` uses 
`WorkflowSingleAgentExample.copyResource(...)`.
   
   **Documentation** (`yaml_agent.md`):
   - Line 253: `copyResource("yaml/yaml_review_analysis_agent.yaml")`
   - Line 257: `copyResource("input_data.txt")`
   
   **Actual code** (`YamlWorkflowAgentExample.java`):
   - Line 63: 
`WorkflowSingleAgentExample.copyResource("yaml/yaml_review_analysis_agent.yaml")`
   - Line 68: `WorkflowSingleAgentExample.copyResource("input_data.txt")`
   
   Unlike `ReActAgentExample` and `WorkflowMultipleAgentExample` which use 
`import static` to allow bare calls, `YamlWorkflowAgentExample` does not have a 
static import, so the class-qualified call is required.
   
   Introduced in PR #705.
   
   **Suggested fix**: Add `import static 
org.apache.flink.agents.examples.WorkflowSingleAgentExample.copyResource` to 
`YamlWorkflowAgentExample.java` and use bare `copyResource(...)` calls, 
consistent with `ReActAgentExample` and `WorkflowMultipleAgentExample`.
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!
   
   ### How to reproduce
   
    -
   
   ### Version and environment
   
    -
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


-- 
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