Chat adapters for Bot Framework Web Chat
Перейти к файлу
sryarama 058f2a26d5
Setting node environment to production (#58)
* Setting node environment to production

* Fix build issues
2023-02-21 15:50:42 -08:00
.github/workflows Setting node environment to production (#58) 2023-02-21 15:50:42 -08:00
.vscode Clean up 2020-04-16 18:56:10 -07:00
__tests__ Users/ersuo/fix message order (#46) 2022-02-07 11:28:15 -08:00
samples/ic3 Clone latest code 2020-04-29 02:31:06 -07:00
src Update Model.d.ts (#52) 2022-10-24 16:23:25 -07:00
.gitignore Add tests 2020-04-15 22:11:42 -07:00
.prettierrc.yml Initial commit 2020-03-27 04:58:19 -07:00
README.md Update README.md 2020-06-19 11:46:00 -07:00
babel.config.json Add IC3 telemetry to adapter (#13) 2020-08-06 14:54:40 -05:00
index.directline.html Porting over prs connectivity manager (#5) 2020-07-12 01:44:06 -07:00
index.html Working ingress of IC3 adapter 2020-04-28 14:59:57 -07:00
jest.config.js Move to setReadyState 2020-04-16 15:54:13 -07:00
package-lock.json Update IC3Client APIs (#26) 2021-05-25 11:24:59 -07:00
package.json upgrade version number 2020-08-18 15:26:20 -07:00
serve.json Working ingress of IC3 adapter 2020-04-28 14:59:57 -07:00
test.js silent test error 2020-06-17 20:09:49 -07:00
tsconfig.json Initial commit 2020-03-27 04:58:19 -07:00
webpack.config.js Clean up 2020-04-17 02:31:05 -07:00

README.md

      _           _               _             _                              _        _                    
  ___| |__   __ _| |_    __ _  __| | __ _ _ __ | |_ ___ _ __   _ __  _ __ ___ | |_ ___ | |_ _   _ _ __   ___ 
 / __| '_ \ / _` | __|  / _` |/ _` |/ _` | '_ \| __/ _ \ '__| | '_ \| '__/ _ \| __/ _ \| __| | | | '_ \ / _ \
| (__| | | | (_| | |_  | (_| | (_| | (_| | |_) | ||  __/ |    | |_) | | | (_) | || (_) | |_| |_| | |_) |  __/
 \___|_| |_|\__,_|\__|  \__,_|\__,_|\__,_| .__/ \__\___|_|    | .__/|_|  \___/ \__\___/ \__|\__, | .__/ \___|
                                         |_|                  |_|                           |___/|_|         

Etqiuette

Test for every fix and feature

This section is not completed yet.

All fix and feature work must come with integration tests. This is to protect your code and make sure your investment will not be broken by others.

Please review our tests under __tests__/stories. These tests are user stories. They include both "today's requirements" and "tomorrow's dreams". We try to push this adapter design to as far as 2 years ahead.

For every new feature, a user story is required. The user story need to be coded as an end-to-end test and placed under this folder for POR.

Design

Egress design

Goals

TODO: Add links to user stories

  • Middleware/enhancer can patch/skip/fork egress activities
    • Asynchronous patch
    • Can be skipped
    • Can be forked into 2+ activities

Ingress design

Goals

TODO: Add links to user stories

  • Anyone who have public access to adapter can send ingress
  • Middleware/enhancer can stop ingress of another middleware/enhancer
    • Web Socket can pause/resume REST API (protocol fallback)
    • Connection manager can stop downstream ingress
  • Middleware can patch/skip/fork the activity of another middleware doing the ingress

Optional goals

  • Easy to ingress a static transcript

Other designs

  • Event target and async iterables are recommended, Observable is welcomed
  • Do not use any operators on Observable
    • Observable operators (for example, flatMap and retryWhen in RxJS) are not welcomed because they are very difficult to debug

Related articles