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.

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

Refactored WS messages functionality #441

Merged
merged 6 commits into from
Aug 29, 2023

Conversation

zAlweNy26
Copy link
Member

Description

I think I improved the way to send ws messages, so that if in the future it should change, we only have to change that specific function. In this way also it's easier for plugins to send directly messages to the chat without waiting for a user input that triggers the tool each time.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas

@@ -217,36 +217,19 @@ def file_to_docs(
blob = Blob(data=file_bytes,
mimetype=content_type,
source=source).from_data(data=file_bytes,
mime_type=content_type)
mime_type=content_type,
path=source)
Copy link
Member Author

@zAlweNy26 zAlweNy26 Aug 29, 2023

Choose a reason for hiding this comment

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

Please don't kill me Piero I know it's not related to the PR, but I also added the path here because it doesn't arrive any source to the parsers. As the documentation says, path will set the source of the Blob

@pieroit pieroit merged commit c6f41a8 into cheshire-cat-ai:develop Aug 29, 2023
2 checks passed
@zAlweNy26 zAlweNy26 deleted the refactored-ws-messages branch September 2, 2023 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants