Client library for the Microsoft Bot Framework Direct Line 3.0 protocol
npm install botframework-directlinejs
Client library for the Microsoft Bot Framework _Direct Line_ protocol.
Used by WebChat and thus (by extension) Emulator, WebChat channel, and Azure Bot Service.
Anyone who is building a Bot Framework JavaScript client who does not want to use WebChat.
If you're currently using WebChat, you don't need to make any changes as it includes this package.
Instead of callbacks or Promises, this library handles async operations using Observables. Try it, you'll like it! For more information, check out RxJS.
You bet.
This is an official Microsoft-supported library, and is considered largely complete. Future changes (aside from supporting future updates to the Direct Line protocol) will likely be limited to bug fixes, performance improvements, tutorials, and samples. The big missing piece here is unit tests.
That said, the public API is still subject to change.
On iOS/iPadOS, when network change from Wi-Fi to cellular, the WebSocket object will be stalled without any errors. This is not detectable nor workaroundable without any additional assistance. The issue is related to an experimental feature named "NSURLSession WebSocket". The feature is enabled by default on iOS/iPadOS 15 and up.
An option named networkInformation can be used to assist the library to detect any connection issues. The option is based on W3C Network Information API and it should implement at least 2 members:
- A type property to indicate the current network type
- When the type is "offline", network is not available and no connection will be made
- A change event should dispatch when the type property change
However, Safari on iOS/iPadOS does not support W3C Network Information API. It is up to web developers to implement the NetworkInformation polyfill.
One effective way to detect network type change is to subscribe to a Server-Sent Events source. The service would send a message every 30 seconds. If network type changed and current network type is no longer available, the connection will be closed prematurely and an error event will be dispatched to the EventSource instance. Upon receiving the error event, the NetworkInformation.type should then change to "offline". The browser would automatically retry the Server-Sent Events connection. Upon receiving an open event, the polyfill should change the type back to "unknown".
If the library is being used in a native iOS/iPadOS app, a less resource-intensive solution would be partially implementing the Network Information API using NWPathMonitor. When network change happens, the NetworkInformation instance should update the type property based on network type and dispatch a change event.
0. Clone this repo
1. npm install
2. npm run build (or npm run watch to rebuild on every change, or npm run prepublishOnly to build production)
There are several ways:
1. Build from scratch and include either /directLine.js (webpacked with rxjs) or lib/directline.js in your app
2. npm install botframework-directlinejs
This library uses RxJs/AjaxObserverable which is meant for use in a DOM environment. That doesn't mean you can't also use it from Node though, you just need to do a couple of extra things:
1. npm install --save ws xhr2
2. Add the following towards the top of your main application file:
``typescript`
global.XMLHttpRequest = require('xhr2');
global.WebSocket = require('ws');
1. If you haven't already, register your bot.
2. Add a DirectLine (not WebChat) channel, and generate a Direct Line Secret. Make sure Direct Line 3.0 is enabled.
3. For testing you can use your Direct Line Secret as a security token, but for production you will likely want to exchange that Secret for a Token as detailed in the Direct Line documentation.
`typescript
import { DirectLine } from 'botframework-directlinejs';
// For Node.js:
// const { DirectLine } = require('botframework-directlinejs');
var directLine = new DirectLine({
secret: / put your Direct Line secret here /,
token: / or put your Direct Line token here (supply secret OR token, not both) /,
domain: / optional: if you are not using the default Direct Line endpoint, e.g. if you are using a region-specific endpoint, put its full URL here /
webSocket: / optional: false if you want to use polling GET to receive messages. Defaults to true (use WebSocket). /,
pollingInterval: / optional: set polling interval in milliseconds. Defaults to 1000 /,
timeout: / optional: a timeout in milliseconds for requests to the bot. Defaults to 20000 /,
conversationStartProperties: { / optional: properties to send to the bot on conversation start /
locale: 'en-US'
}
});
`
`typescript`
directLine
.postActivity({
from: { id: 'myUserId', name: 'myUserName' }, // required (from.name is optional)
type: 'message',
text: 'a message for you, Rudy'
})
.subscribe(
id => console.log('Posted activity, assigned ID ', id),
error => console.log('Error posting activity', error)
);
You can also post messages with attachments, and non-message activities such as events, by supplying the appropriate fields in the activity.
`typescript`
directLine.activity$.subscribe(activity => console.log('received activity ', activity));
You can use RxJS operators on incoming activities. To see only message activities:
`typescript`
directLine.activity$
.filter(activity => activity.type === 'message')
.subscribe(message => console.log('received message ', message));
Direct Line will helpfully send your client a copy of every sent activity, so a common pattern is to filter incoming messages on from:
`typescript`
directLine.activity$
.filter(activity => activity.type === 'message' && activity.from.id === 'yourBotHandle')
.subscribe(message => console.log('received message ', message));
Subscribing to either postActivity or activity$ will start the process of connecting to the bot. Your app can listen to the connection status and react appropriately :
`typescript
import { ConnectionStatus } from 'botframework-directlinejs';
directLine.connectionStatus$.subscribe(connectionStatus => {
switch (connectionStatus) {
case ConnectionStatus.Uninitialized: // the status when the DirectLine object is first created/constructed
case ConnectionStatus.Connecting: // currently trying to connect to the conversation
case ConnectionStatus.Online: // successfully connected to the converstaion. Connection is healthy so far as we know.
case ConnectionStatus.ExpiredToken: // last operation errored out with an expired token. Your app should supply a new one.
case ConnectionStatus.FailedToConnect: // the initial attempt to connect to the conversation failed. No recovery possible.
case ConnectionStatus.Ended: // the bot ended the conversation
}
});
`
If your app created your DirectLine object by passing a token, DirectLine will refresh that token every 15 minutes.
Should your client lose connectivity (e.g. close laptop, fail to pay Internet access bill, go under a tunnel), connectionStatus$
will change to . Your app can request a new token from its server, which should call
the Reconnect API.
The resultant Conversation object can then be passed by the app to DirectLine.
`typescript`
var conversation = / a Conversation object obtained from your app's server /;
directLine.reconnect(conversation);
When using DirectLine with WebChat, closing the current tab or refreshing the page will create a new conversation in most cases. You can resume an existing conversation to keep the user in the same context.
When using a secret you can resume a conversation by:
- Storing the conversationid (in a _permanent_ place, like local storage)
- Giving this value back while creating the DirectLine object along with the secret
`typescript
import { DirectLine } from 'botframework-directlinejs';
const dl = new DirectLine({
secret: / SECRET /,
conversationId: / the conversationid you stored from previous conversation /
});
`
When using a token you can resume a conversation by:
- Storing the conversationid and your token (in a _permanent_ place, like local storage)
- Calling the DirectLine reconnect API yourself to get a refreshed token and a streamurl
- Creating the DirectLine object using the ConversationId, Token, and StreamUrl
`typescript
import { DirectLine } from 'botframework-directlinejs';
const dl = new DirectLine({
token: / the token you retrieved while reconnecting /,
streamUrl: / the streamUrl you retrieved while reconnecting /,
conversationId: / the conversationid you stored from previous conversation /
});
`
Getting any history that Direct Line has cached : you can retrieve history using watermarks:
You can see the watermark as an _activity 'bookmark'_. The resuming scenario will replay all the conversation activities from the watermark you specify.
`typescript
import { DirectLine } from 'botframework-directlinejs';
const dl = new DirectLine({
token: / the token you retrieved while reconnecting /,
streamUrl: / the streamUrl you retrieved while reconnecting /,
conversationId: / the conversationid you stored from previous conversation /,
watermark: / a watermark you saved from a previous conversation /,
webSocket: false
});
``
This project welcomes contributions and suggestions. Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct.
For more information see the Code of Conduct FAQ or
contact opencode@microsoft.com with any additional questions or comments.
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
Copyright (c) Microsoft Corporation. All rights reserved.