All notable changes to this project will be documented in this file. See standard-version for commit guidelines.
- Fixed the casing issue in readme to show gifs
- Re Added repository link in Package.json.
- Regex Validation of default form field of phone number fix to allow 0 and +91 at starting.
- Both Demo video align in same line.
- Add HomePage link in Package.json.
- Added customizable
chatBotHeight
andchatBotWidth
props to control the chatbot's dimensions of height and width. - Added customizable
leadFormHeader
,leadFormDescription
, andleadFormButtonText
props for dynamic form text of leadForm.
- Add a demo video of lead form in Readme.md file.
- For Approach Feature update link of Gemini text generation docs.
- Introduced the goodFormatting feature which adds instructions for well-structured, readable responses with appropriate formatting by passing true value.
- Introduced the tone If specified, instructs the model to respond in the requested tone and default formal tone is used.
- Introduced the useEmoji feature which adds emoji in response by passing true.
- Introduced the Approach feature, which allows users to set a zero-shot approach for the chatbot or language model
- Added support for one-shot or few-shot approaches,You can define a Array of json object like this [{user : "text",agent:"text"}].
- fixed casing issue of ChatBot , made as per README
- Issue of leadform ui solve
- Add try and catch in api calling
- LeadForm Feature:
- Added the ability to enable a customizable lead form through the
enableLeadForm
flag. - The form can be default with fields such as
Company Name
,Email
,Phone Number
, andCustom Fields
(like dropdowns and text inputs). - You can configure the form position with
enableFormAt
and provide various field options, such astitle
,placeholder
,type
,validationMessage
, andrequired
to add your own fields. - Optionally, the form can be linked to an API to submit the collected data using
submitApiEndPoint
,submitApiAccessToken
, andAPIFormHttpMethod
. - Fields are optional and can be added or removed from the form dynamically based on configuration.
- Added the ability to enable a customizable lead form through the
- Fixed an issue where the textPosition change type was incorrectly set to string instead of boolean.
- Fixed the image format and changed the image type to
embeddedUri
.
- Users can now add a backend endpoint (
apiStoreResponseDataEndpoint
) to store every conversation between the chatbot and the user. - Users can also add an optional access token (
accessTokenOfApi
) for authentication. It is not mandatory. - users can also add http method(
ApiHttpMethod
) (eg. post,put,get) based on backend api and also it is optional and default it take post.
- Fixed an issue with file input and upload functionality.
- Fixed the image path handling issue.