Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: AI-179: Handle status update messages #8

Merged
merged 1 commit into from
Oct 21, 2024
Merged

feat: AI-179: Handle status update messages #8

merged 1 commit into from
Oct 21, 2024

Conversation

efunneko
Copy link
Collaborator

This PR enhances the Slack input and output components:

  • Improves handling of streamed responses and status updates
  • Adds context blocks for acknowledgement and status messages
  • Refactors message handling logic for better clarity
  • Removes unnecessary code and improves error handling
  • Enhances markdown formatting fixes for Slack compatibility

@efunneko
feat: AI-179: Add handling for status messages and add a Response Com…
106b39e 
…plete status when the response complete event arrives
@efunneko efunneko self-assigned this Oct 20, 2024
@gitstream-cm gitStream.cm
Copy link

gitstream-cm bot commented Oct 20, 2024

Please mark whether you used Copilot to assist coding in this PR

  • Copilot Assisted

cyrus2281
cyrus2281 approved these changes Oct 21, 2024
View reviewed changes
Copy link

@cyrus2281 cyrus2281 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@efunneko efunneko merged commit ac5a17d into main Oct 21, 2024
3 checks passed
@efunneko efunneko deleted the ed/status_updates branch October 24, 2024 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@cyrus2281 cyrus2281 cyrus2281 approved these changes

Assignees

@efunneko efunneko

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@efunneko @cyrus2281