Shared models SDK and UI. REPOSITORY MOVED
Перейти к файлу
Lars Liden 3936861c65 fix: security vulnerabilities 2018-09-12 09:38:10 -07:00
.circleci Add caching to circle CI config, and add status badge (#102) 2018-05-31 10:55:21 -07:00
.vscode
scripts
src fix: text 2018-09-07 15:39:47 -07:00
tools
.editorconfig
.gitignore
.travis.yml chore: use commitlint instead of validate-commit-msg (#109) 2018-06-06 11:46:36 -07:00
CONTRIBUTING.md
LICENSE
README.md fix: package-lock.json and update readme (#117) 2018-07-10 16:47:22 -07:00
appveyor.yml Skip building branches with PR (#103) 2018-05-31 11:36:28 -07:00
code-of-conduct.md
package-lock.json fix: security vulnerabilities 2018-09-12 09:38:10 -07:00
package.json fix: security vulnerabilities 2018-09-12 09:38:10 -07:00
rollup.config.ts
tsconfig.json
tslint.json fix: tslint 2018-09-06 15:20:00 -07:00

README.md

ConversationLearner-Models

Models for ConversationLearner

styled with prettier Travis CircleCI AppVeyor

Usage

This library is a collection of types, interfaces, and utilities shared across other ConversationLearner repositories:

git clone https://github.com/Microsoft/conversationlearner-models.git conversationlearner-models
cd conversationlearner-models
npm install
npm run build
npm test

Importing library

import * as models from '@conversationlearner/models'

NPM scripts

  • npm t: Run test suite
  • npm start: Run npm run build in watch mode
  • npm run test:watch: Run test suite in interactive watch mode
  • npm run test:prod: Run linting and generate coverage
  • npm run build: Generate bundles and typings, create docs
  • npm run lint: Lints code
  • npm run commit: Commit using conventional commit style (husky will tell you to use it if you haven't 😉)

Semantic Release

Semantic release works by analyzing all commits that have occurred since the last release, computing the next version to increment based on the most significant commit found, then tagging and publishing a new package with that version.

See: https://semantic-release.gitbooks.io/semantic-release/content/#how-does-it-work

In order to analyze the commit messages reliably they must be in a known format. To help writing these commits there is a tool at npm run commit which acts a wizard walking you through the options.

For most use cases the only change required is to type a special word in front of your normal commit messages. Instead of "add function to compute X" put "feat: add function to compute X". Based on the rules "feat" is mapped to a "minor" release.

Video Demo: https://youtu.be/qf7c-KxBBZc?t=37s