deep-chat

When developers start using Deep Chat and want to attempt to change its style, they would usually first try to use the style property. In the previous versions this did not do anything and they would then have to search for specific properties for what they want to change. To make the lives of new and old developers easier, we have moved the containerStyle property to style to create a simpler style changing experience.

The intro panel's styling and JavaScript can now be controlled via the htmlClassUtilities property. This opens up opportunities to reuse consistent styling and give JavaScript access to the parent state.

• You can now render your own custom elements inside messages using the new messages HTML API.
• You can force the chat to scroll down using the new scrollToBottom method.
• The introMessage property now requires its value to be defined using a JSON in order to denote the use of text vs custom elements.
• The messageStyles property now contains a html key to allow your custom elements to be styled the way you need them.
• This update also contains other small bug fixes.

Demo property has been moved from the directConnection object to the parent level. This was done for both; making it easier for the user to configure the demo and more importantly in preparation for adding more connection properties into the component where having demo makes more sense in the parent level.

When no connection properties/attributes (request or directConnection) are set or they use incorrect values, the component defaults to the demo mode which additionally now guides developers how to set it up correctly.

We are excited to release a new addition to the Deep Chat website - the Playground. Here you will be able to create, configure and use Deep Chat components without needing to write any code. Check it out in the official Playground page to get started!

The OpenAI and Cohere interfaces have been updated to reflect the latest changes in their API. The OpenAI chat interface also has the systemPrompt changed to system_prompt to keep the syntax consistent with the rest of the interface.
This updates also includes bug fixes where the passed in configuration object for existing services had their properties removed as part of a cleanup process, hence those properties could not be reused when using the object in another component. This has now been fixed.

Updating the syntax or StabilityAI intro panel text.

Previously when text was streamed and the component either had avatars or names - the consecutive streams would include the previously streamed text. Additionally the clearMessages method was not clearing error messages.

These bugs are now fixed.

If you had the requestBodyLimits property set to 0 or below and were changing the messages array in the requestInterceptor or handler functions, you may have been affecting the state inside the Deep Chat component. This has now been fixed as the messages array is dereferenced before it leaves the component.

Adding a new request handler function into the component which is used to override the connection behaviour and allow developers to use their own code for making requests.

The clearMessages method was not fully clearing the internal state so when the user would call getMessages they would still get the messages before the clear. This bug is now fixed.

• The expected response object from a custom service has been changed to Response in order to simplify the required setup.
• This release also contains a minor websocket fix where the reconnection logic no longer attempts to connect if the component is no longer present.

If a websocket connection fails, the component will reattempt to connect every 5 seconds.

We have replaced the old onMessagesCleared event with onClearMessages to better reflect when it is triggered and keep the syntax similar to the clearMessages method.

Additionally, when the websocket url did not start with "ws:" the component would throw an error that was not caught. This is now fixed.

Adding a new method called clearMessages to remove all messages in the chat. This is also accompanied by a onMessagesCleared event to help track chat state.

When using Svelte to develop a browser app - property values no longer need to be stringified.

The requestInterceptor now supports asynchronous functions to do other processing before the actual request is sent out to the target.

Deep Chat is now compatible with build tools/browsers that use JavaScript ES5/2015 syntax.

Features:

• Websockets
• Speech To Text performance optimiziations
• Configure the input style on focus
• Custom demo response message
• Improving error handling
• Stream server-sent events and regular message responses
• Bug fixes