React hook for easily building custom Rasa assistants.
npm i react-rasa-assistant
import useBot from 'react-rasa-assistant'
Basic:
const Assistant = () => {
const {
msgHistory, onInputRef, userText, setUserText, sendUserText,
selectOption, restartSession,
} =
useBot({sockUrl: '<your socket url>'})
return <>
{msgHistory.map((msg, msgIdx) => {
if (msg.text)
return <div key={msg.ts + '-txt'}>
{{in: '< ', out: '> '}[msg.direction]}
{msg.text}
</div>
if ((msg.quick_replies || msg.buttons))
return <div key={msg.ts + '-btngroup'}>
{(msg.quick_replies || msg.buttons).map((opt, optIdx) =>
<button
key={opt.payload}
onClick={() => selectOption(msgIdx, optIdx)}
>
{opt.title}
</button>
)}
</div>
// Also handle any other custom properties (if any)
})}
<input
value={userText}
onChange={e => setUserText(e.target.value)}
ref={onInputRef}
/>
<button onClick={sendUserText}>Send</button>
<br /><button onClick={restartSession}>Restart</button>
</>
}
Handle custom responses:
const Assistant = () => {
const {
msgHistory, onInputRef, userText, setUserText, sendUserText,
selectOption, botUtter, restartSession,
} =
useBot({
sockUrl: '<your socket url>',
onUtter: msg => {
if (
msg.direction === 'in'
&& !msg.text
&& !msg.quick_replies
&& !msg.buttons
) {
console.log('This is a custom message!', msg)
botUtter({text: 'I just sent you a custom message!'})
}
},
})
return ...
}
const {
msgHistory, onInputRef, userText, setUserText,
sendUserText, selectOption, botUtter, restartSession,
}
= useBot({sockUrl, sockOpts, initSessionId, initMsg, onError, onUtter})
-
sockUrl
: Full socket URL -
sockOpts
: Advanced socket options. See here for a full reference. -
initSessionId
: An optional session id that may be used to continue a previous session. -
initMsg
: An optional text to be sent in the beginning of the conversation. Alternatively an object with thetitle
andpayload
attributes is supported too; in which case thetitle
will be shown in the conversation and thepayload
will be sent to the server, just like case with buttons. -
onError(error)
: An optional handler that gets called each time the socket emits an error. Error object schema:type
: Name of the socket socket error eventpayload
: The error object exactly as emitted by the socket
-
onUtter(msg)
: An optional handler that is called for each message sent / received. See the details of the message object at the end of the section.
-
msgHistory
: An array of message objects. See the details of the message object at the end of the section. -
onInputRef(el)
: A standard React ref callback that expects the native input element as its sole parameter. Passing the ref this way to the library allows it to handle behavior such as auto focusing and blurring. If this is not something you want, just don't use this and handle those behaviors yourself the way you want. -
userText
: The current value of the text that has not yet been sent. -
setUserText(text)
: Setter method foruserText
above. -
sendUserText()
: Send the currentuserText
to the assistant and empty its value. -
selectOption(msgIdx, optIdx)
: Select an option provided by a message with thebuttons
orquick_replies
property. Args:-
msgIdx
: The index of the message that this button is a part of. This is required as in the case of quick replies, the button group is removed after an option is selected. -
optIdx
: The index of the option to select in thebuttons
orquick_replies
array.
-
-
botUtter(msg)
: Send a message from the bot, as if it was the bot talking. This is intended to be used to handle custom responses. See the details of the message object, which is the only parameter, at the end of the section. -
restartSession()
: Clear the message history and restart the session.
-
ts
: Message timestamp -
direction
: Eitherin
(for "incoming") orout
(for "outgoing") -
text
: The message text. Optional -
buttons
: A list of button objects. Optional. Button object schema:title
: The button titlepayload
: The button payload. Should be a valid Rasa intent.
-
quick_replies
: A list of button objects. Optional Quick replies only differ from buttons with their ability of disappearing after being clicked on. Button object schema:title
: The button titlepayload
: The button payload. Should be a valid Rasa intent.
-
metadata
: Potential metadata as sent by Rasa. Optional
In case of a custom response, custom properties matching the ones in the custom response will exist as well.
In React Native the transports
socket option needs to be
explicitly provided with the value ['websocket']
:
useBot({
sockUrl: '<your socket url>',
sockOpts: {transports: ['websocket']},
...
}))
The reason for this is that the default value for that option is
['polling', 'websocket']
but polling
isn't supported on React
Native. The Socket.io client doesn't automatically switch to
Websocket connection if polling is failing, so this must be
explicitly configured.
Visuals of an ugly assistant made with this hook: