chore: Update example to print follow up event

[hanzeINGH]

Change-Id: I37bd0a8ccc9e74c010ee204442dfde291132e6c3

[coderabbitai]

Walkthrough

The event handling logic in the chat example was refined to print message content only for follow-up messages upon conversation completion, while other messages print token usage. Executor shutdown was moved exclusively to the DONE event handler, removing it from the CONVERSATION_CHAT_COMPLETED block. Additionally, the MessageType class gained an @EqualsAndHashCode annotation.

Changes

File(s)	Change Summary
example/src/main/java/example/chat/StreamChatExample.java	Added conditional printing for follow-up messages on CONVERSATION_CHAT_COMPLETED. Moved executor shutdown exclusively to the DONE event handler.
api/src/main/java/com/coze/openapi/client/connversations/message/model/MessageType.java	Added Lombok @EqualsAndHashCode annotation to generate equals() and hashCode() methods automatically.

Poem

In the chat stream’s gentle hum,
New branches bloom, old flows succumb.
Now “DONE” calls the shutdown tune,
While chat completes with a message soon.
Rabbits cheer this tidy split—
Code hops forward, bit by bit! 🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between ae723f4 and f5efd52.

📒 Files selected for processing (2)

• api/src/main/java/com/coze/openapi/client/connversations/message/model/MessageType.java (1 hunks)
• example/src/main/java/example/chat/StreamChatExample.java (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• api/src/main/java/com/coze/openapi/client/connversations/message/model/MessageType.java

🚧 Files skipped from review as they are similar to previous changes (1)

• example/src/main/java/example/chat/StreamChatExample.java

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: test (Java 11 on Windows)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🔭 Outside diff range comments (1)

example/src/main/java/example/chat/StreamChatExample.java (1)

80-80: ⚠️ Potential issue

Potential redundant executor shutdown

There's now a redundant call to shutdownExecutor() here. The executor is already shut down when the DONE event is received (line 64), which could lead to attempting to shut down an already terminated executor.

Consider one of these approaches:

1. Remove this line since shutdown now happens in the DONE event handler
2. Add a check to only shut down if not already terminated
3. Add a comment explaining this is a fallback in case no DONE event is received

-    coze.shutdownExecutor();
+    // Only shut down if not already terminated by DONE event
+    if (!coze.isExecutorTerminated()) {
+        coze.shutdownExecutor();
+    }

🧹 Nitpick comments (1)

example/src/main/java/example/chat/StreamChatExample.java (1)

74-74: Update comment to use English instead of Chinese

Line 74 contains a comment in Chinese. For consistency with the rest of the codebase, consider translating it to English.

-    // 为了防止程序立即退出，添加一个简单的等待
+    // Add a simple wait to prevent the program from exiting immediately

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 209fc79 and ae723f4.

📒 Files selected for processing (1)

• example/src/main/java/example/chat/StreamChatExample.java (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: test (Java 17 on Windows)
• GitHub Check: test (Java 11 on Windows)

🔇 Additional comments (2)

example/src/main/java/example/chat/StreamChatExample.java (2)

59-62: Good addition for visibility of completed messages

Adding this print statement provides better visibility into the complete message when a conversation is completed, which is helpful for debugging and monitoring purposes.

---

63-65: Good separation of shutdown logic

Moving the executor shutdown to the DONE event handler is a proper separation of concerns. This ensures that the executor is only shut down when all processing is truly complete rather than on conversation completion.