talksuite-cli

• Usage
• Commands

Usage

INSTALL
$ npm install -g @talksuite/talksuite-cli

USAGE
$ ts COMMAND
running command...
$ ts (-v|--version|version)
talksuite-cli/x.y.z [ARCH] node-[NODEVERS]
$ ts --help [COMMAND]

Commands

• ts create-bot-template ORGID BOTID NAME
• ts export-bots CONTENTDIR [ORGID] [BOTID]
• ts export-content CONTENTDIR [ORGID] [PROJECTID]
• ts help [COMMAND]
• ts import-bots CONTENTDIR [ORGID] [BOTID]
• ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]
• ts list-bots [ORGID]
• ts list-dialogues [ORGID] [PROJECTID]
• ts list-orgs
• ts list-processes [ORGID]
• ts list-projects [ORGID]
• ts login [ENV] [EMAIL] [PASSWORD]
• ts ludown-to-luis SOURCE OUT
• ts luis-to-ludown SOURCE OUT
• ts migrate-bot ORGID BOTID TEMPLATENAME
• ts update-all-processes NAME HOURS MINUTES [ORGID]
• ts validate-bots ORGID [BOTID]
• ts validate-content CONTENTDIR
• ts validate-project ORGID PROJECTID

ts create-bot-template ORGID BOTID NAME

Create a bot template to be used to ensure the correct configuration of all bots of the same type

USAGE
  $ ts create-bot-template ORGID BOTID NAME

ARGUMENTS
  ORGID  org ID or name containing the bot to template
  BOTID  bot ID or name of the bot to template
  NAME   name of the template

See code: src\commands\create-bot-template.js

ts export-bots CONTENTDIR [ORGID] [BOTID]

Exports bots for backup or editing locally

USAGE
  $ ts export-bots CONTENTDIR [ORGID] [BOTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  BOTID       bot ID or name

See code: src\commands\export-bots.js

ts export-content CONTENTDIR [ORGID] [PROJECTID]

exports dialogues languages and projects to the local file system

USAGE
  $ ts export-content CONTENTDIR [ORGID] [PROJECTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  PROJECTID   project ID or name

OPTIONS
  -g, --guid  Stores in a human readable folder structure.

See code: src\commands\export-content.js

ts help [COMMAND]

display help for ts

USAGE
  $ ts help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

ts import-bots CONTENTDIR [ORGID] [BOTID]

Imports bots from local files into talksuite

USAGE
  $ ts import-bots CONTENTDIR [ORGID] [BOTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  BOTID       bot ID or name

See code: src\commands\import-bots.js

ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]

Imports the local copies of dialogues/languages and projects into talksuite

USAGE
  $ ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]

ARGUMENTS
  CONTENTDIR       directory to import from
  ORGID            org ID or name to import into
  PROJECTID        org ID or name to import
  REMOTEPROJECTID  org ID or name to import into

OPTIONS
  -d, --delete           Remove Content and projects that aren't being imported.
  -i, --ignore           ignore import order pre-checking.
  -v, --disableValidate  Disable cross dialogue validation of the dialogues.

See code: src\commands\import-content.js

ts list-bots [ORGID]

Lists the bots in an organisation talksuite.

USAGE
  $ ts list-bots [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-bots.js

ts list-dialogues [ORGID] [PROJECTID]

Lists the dialogues in an organisation talksuite.

USAGE
  $ ts list-dialogues [ORGID] [PROJECTID]

ARGUMENTS
  ORGID      org ID or name
  PROJECTID  org ID or name

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-dialogues.js

ts list-orgs

Lists all your organisations in talksuite.

USAGE
  $ ts list-orgs

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-orgs.js

ts list-processes [ORGID]

Lists the bots and their processes in an organisation talksuite.

USAGE
  $ ts list-processes [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-processes.js

ts list-projects [ORGID]

Lists the projects in a talksuite organisation.

USAGE
  $ ts list-projects [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-projects.js

ts login [ENV] [EMAIL] [PASSWORD]

login to talksuite to allow command line access

USAGE
  $ ts login [ENV] [EMAIL] [PASSWORD]

ARGUMENTS
  ENV       [default: produks] base url to create http calls from (only applicable for internal talksuite development)
            if you're scripting a login use produks

  EMAIL     Email that you would use to log into talksuite

  PASSWORD  password to use

See code: src\commands\login.js

ts ludown-to-luis SOURCE OUT

Convert a ludown file into a LUIS json file.

USAGE
  $ ts ludown-to-luis SOURCE OUT

ARGUMENTS
  SOURCE  source file
  OUT     output file

DESCRIPTION
  example use
  ts luis-to-ludown .\build\BotServices\luis\iTrent.json .\tmp.txt

  use the text document to add each utterance as a line
  then use something like
  ts ludown-to-luis .\tmp.txt .\build\BotServices\luis\iTrent.json
  will write it back to the luis.json
  then compare ?
  i've never done whole file though so i'm not 100 % on this
  other option would be to build a text file like:

  ## general.changeLanguage 
  - can we use pirate english 
  - can you change my lingo? 
  - can you speak like a pirate 
  - can you speak pirate 
  - change language 
  - change language of the bot 
  - change local 
  - change location 
  - change my languahae 
  - change my local 
  - change my location 
  - do you speak any other languages 
  - do you speak any other languages? 
  - how do i change my location? 
  - how do i change your dialect? 
  - how do i change your language? 
  - how do i change your local? 
  - language 

  and then convert that and manually merge that into the luis json file

See code: src\commands\ludown-to-luis.js

ts luis-to-ludown SOURCE OUT

Convert a luis json file into a ludown file.

USAGE
  $ ts luis-to-ludown SOURCE OUT

ARGUMENTS
  SOURCE  source file
  OUT     output file

See code: src\commands\luis-to-ludown.js

ts migrate-bot ORGID BOTID TEMPLATENAME

Update a Bot from a template

USAGE
  $ ts migrate-bot ORGID BOTID TEMPLATENAME

ARGUMENTS
  ORGID         org ID or name
  BOTID         bot ID or name
  TEMPLATENAME  bot ID or name

OPTIONS
  -v, --verbose  Turn on the additional log messages.

See code: src\commands\migrate-bot.js

ts update-all-processes NAME HOURS MINUTES [ORGID]

Update all processes on all bots in an org.

USAGE
  $ ts update-all-processes NAME HOURS MINUTES [ORGID]

ARGUMENTS
  NAME     The name of the process
  HOURS    The hour when the process should trigger
  MINUTES  The minute when the process should trigger
  ORGID    org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\update-all-processes.js

ts validate-bots ORGID [BOTID]

Compare a bot against its template showing any misconfigurations and potentially performing simple fixes

USAGE
  $ ts validate-bots ORGID [BOTID]

ARGUMENTS
  ORGID  org ID or name
  BOTID  bot ID or name

OPTIONS
  -u, --update  update constants that are not valid against the templates

See code: src\commands\validate-bots.js

ts validate-content CONTENTDIR

validate local dialogues to isolate problems

USAGE
  $ ts validate-content CONTENTDIR

ARGUMENTS
  CONTENTDIR  directory to scan

See code: src\commands\validate-content.js

ts validate-project ORGID PROJECTID

Validate dialogues and languages of the specified project against global and themselves

USAGE
  $ ts validate-project ORGID PROJECTID

ARGUMENTS
  ORGID      Organisation ID that contains the project
  PROJECTID  Project ID or Name to validate

See code: src\commands\validate-project.js

• ts create-bot-template ORGID BOTID NAME
• ts export-bots CONTENTDIR [ORGID] [BOTID]
• ts export-content CONTENTDIR [ORGID] [PROJECTID]
• ts help [COMMAND]
• ts import-bots CONTENTDIR [ORGID] [BOTID]
• ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]
• ts list-bots [ORGID]
• ts list-dialogues [ORGID] [PROJECTID]
• ts list-orgs
• ts list-processes [ORGID]
• ts list-projects [ORGID]
• ts login [ENV] [EMAIL] [PASSWORD]
• ts ludown-to-luis SOURCE OUT
• ts luis-to-ludown SOURCE OUT
• ts migrate-bot ORGID BOTID TEMPLATENAME
• ts update-all-processes NAME HOURS MINUTES [ORGID]
• ts validate-bots ORGID [BOTID]
• ts validate-content CONTENTDIR
• ts validate-project ORGID PROJECTID

ts create-bot-template ORGID BOTID NAME

Create a bot template to be used to ensure the correct configuration of all bots of the same type

USAGE
  $ ts create-bot-template ORGID BOTID NAME

ARGUMENTS
  ORGID  org ID or name containing the bot to template
  BOTID  bot ID or name of the bot to template
  NAME   name of the template

See code: src\commands\create-bot-template.js

ts export-bots CONTENTDIR [ORGID] [BOTID]

Exports bots for backup or editing locally

USAGE
  $ ts export-bots CONTENTDIR [ORGID] [BOTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  BOTID       bot ID or name

See code: src\commands\export-bots.js

ts export-content CONTENTDIR [ORGID] [PROJECTID]

exports dialogues languages and projects to the local file system

USAGE
  $ ts export-content CONTENTDIR [ORGID] [PROJECTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  PROJECTID   project ID or name

OPTIONS
  -g, --guid  Stores in a human readable folder structure.

See code: src\commands\export-content.js

ts help [COMMAND]

display help for ts

USAGE
  $ ts help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

ts import-bots CONTENTDIR [ORGID] [BOTID]

Imports bots from local files into talksuite

USAGE
  $ ts import-bots CONTENTDIR [ORGID] [BOTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  BOTID       bot ID or name

See code: src\commands\import-bots.js

ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]

Imports the local copies of dialogues/languages and projects into talksuite

USAGE
  $ ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]

ARGUMENTS
  CONTENTDIR       directory to import from
  ORGID            org ID or name to import into
  PROJECTID        org ID or name to import
  REMOTEPROJECTID  org ID or name to import into

OPTIONS
  -d, --delete           Remove Content and projects that aren't being imported.
  -i, --ignore           ignore import order pre-checking.
  -v, --disableValidate  Disable cross dialogue validation of the dialogues.

See code: src\commands\import-content.js

ts list-bots [ORGID]

Lists the bots in an organisation talksuite.

USAGE
  $ ts list-bots [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-bots.js

ts list-dialogues [ORGID] [PROJECTID]

Lists the dialogues in an organisation talksuite.

USAGE
  $ ts list-dialogues [ORGID] [PROJECTID]

ARGUMENTS
  ORGID      org ID or name
  PROJECTID  org ID or name

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-dialogues.js

ts list-orgs

Lists all your organisations in talksuite.

USAGE
  $ ts list-orgs

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-orgs.js

ts list-processes [ORGID]

Lists the bots and their processes in an organisation talksuite.

USAGE
  $ ts list-processes [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-processes.js

ts list-projects [ORGID]

Lists the projects in a talksuite organisation.

USAGE
  $ ts list-projects [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-projects.js

ts login [ENV] [EMAIL] [PASSWORD]

login to talksuite to allow command line access

USAGE
  $ ts login [ENV] [EMAIL] [PASSWORD]

ARGUMENTS
  ENV       [default: produks] base url to create http calls from (only applicable for internal talksuite development)
            if you're scripting a login use produks

  EMAIL     Email that you would use to log into talksuite

  PASSWORD  password to use

See code: src\commands\login.js

ts ludown-to-luis SOURCE OUT

Convert a ludown file into a LUIS json file.

USAGE
  $ ts ludown-to-luis SOURCE OUT

ARGUMENTS
  SOURCE  source file
  OUT     output file

DESCRIPTION
  example use
  ts luis-to-ludown .\build\BotServices\luis\iTrent.json .\tmp.txt

  use the text document to add each utterance as a line
  then use something like
  ts ludown-to-luis .\tmp.txt .\build\BotServices\luis\iTrent.json
  will write it back to the luis.json
  then compare ?
  i've never done whole file though so i'm not 100 % on this
  other option would be to build a text file like:

  ## general.changeLanguage 
  - can we use pirate english 
  - can you change my lingo? 
  - can you speak like a pirate 
  - can you speak pirate 
  - change language 
  - change language of the bot 
  - change local 
  - change location 
  - change my languahae 
  - change my local 
  - change my location 
  - do you speak any other languages 
  - do you speak any other languages? 
  - how do i change my location? 
  - how do i change your dialect? 
  - how do i change your language? 
  - how do i change your local? 
  - language 

  and then convert that and manually merge that into the luis json file

See code: src\commands\ludown-to-luis.js

ts luis-to-ludown SOURCE OUT

Convert a luis json file into a ludown file.

USAGE
  $ ts luis-to-ludown SOURCE OUT

ARGUMENTS
  SOURCE  source file
  OUT     output file

See code: src\commands\luis-to-ludown.js

ts migrate-bot ORGID BOTID TEMPLATENAME

Update a Bot from a template

USAGE
  $ ts migrate-bot ORGID BOTID TEMPLATENAME

ARGUMENTS
  ORGID         org ID or name
  BOTID         bot ID or name
  TEMPLATENAME  bot ID or name

OPTIONS
  -v, --verbose  Turn on the additional log messages.

See code: src\commands\migrate-bot.js

ts update-all-processes NAME HOURS MINUTES [ORGID]

Update all processes on all bots in an org.

USAGE
  $ ts update-all-processes NAME HOURS MINUTES [ORGID]

ARGUMENTS
  NAME     The name of the process
  HOURS    The hour when the process should trigger
  MINUTES  The minute when the process should trigger
  ORGID    org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\update-all-processes.js

ts validate-bots ORGID [BOTID]

Compare a bot against its template showing any misconfigurations and potentially performing simple fixes

USAGE
  $ ts validate-bots ORGID [BOTID]

ARGUMENTS
  ORGID  org ID or name
  BOTID  bot ID or name

OPTIONS
  -u, --update  update constants that are not valid against the templates

See code: src\commands\validate-bots.js

ts validate-content CONTENTDIR

validate local dialogues to isolate problems

USAGE
  $ ts validate-content CONTENTDIR

ARGUMENTS
  CONTENTDIR  directory to scan

See code: src\commands\validate-content.js

ts validate-project ORGID PROJECTID

Validate dialogues and languages of the specified project against global and themselves

USAGE
  $ ts validate-project ORGID PROJECTID

ARGUMENTS
  ORGID      Organisation ID that contains the project
  PROJECTID  Project ID or Name to validate

See code: src\commands\validate-project.js

• ts create-bot-template ORGID BOTID NAME
• ts export-bots CONTENTDIR [ORGID] [BOTID]
• ts export-content CONTENTDIR [ORGID] [PROJECTID]
• ts help [COMMAND]
• ts import-bots CONTENTDIR [ORGID] [BOTID]
• ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]
• ts list-bots [ORGID]
• ts list-dialogues [ORGID] [PROJECTID]
• ts list-orgs
• ts list-processes [ORGID]
• ts list-projects [ORGID]
• ts login [ENV] [EMAIL] [PASSWORD]
• ts ludown-to-luis SOURCE OUT
• ts luis-to-ludown SOURCE OUT
• ts migrate-bot ORGID BOTID TEMPLATENAME
• ts update-all-processes NAME HOURS MINUTES [ORGID]
• ts validate-bots ORGID [BOTID]
• ts validate-content CONTENTDIR
• ts validate-project ORGID PROJECTID

ts create-bot-template ORGID BOTID NAME

Create a bot template to be used to ensure the correct configuration of all bots of the same type

USAGE
  $ ts create-bot-template ORGID BOTID NAME

ARGUMENTS
  ORGID  org ID or name containing the bot to template
  BOTID  bot ID or name of the bot to template
  NAME   name of the template

See code: src\commands\create-bot-template.js

ts export-bots CONTENTDIR [ORGID] [BOTID]

Exports bots for backup or editing locally

USAGE
  $ ts export-bots CONTENTDIR [ORGID] [BOTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  BOTID       bot ID or name

See code: src\commands\export-bots.js

ts export-content CONTENTDIR [ORGID] [PROJECTID]

exports dialogues languages and projects to the local file system

USAGE
  $ ts export-content CONTENTDIR [ORGID] [PROJECTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  PROJECTID   project ID or name

OPTIONS
  -g, --guid  Stores in a human readable folder structure.

See code: src\commands\export-content.js

ts help [COMMAND]

display help for ts

USAGE
  $ ts help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

ts import-bots CONTENTDIR [ORGID] [BOTID]

Imports bots from local files into talksuite

USAGE
  $ ts import-bots CONTENTDIR [ORGID] [BOTID]

ARGUMENTS
  CONTENTDIR  directory to output to
  ORGID       org ID or name
  BOTID       bot ID or name

See code: src\commands\import-bots.js

ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]

Imports the local copies of dialogues/languages and projects into talksuite

USAGE
  $ ts import-content CONTENTDIR [ORGID] [PROJECTID] [REMOTEPROJECTID]

ARGUMENTS
  CONTENTDIR       directory to import from
  ORGID            org ID or name to import into
  PROJECTID        org ID or name to import
  REMOTEPROJECTID  org ID or name to import into

OPTIONS
  -d, --delete           Remove Content and projects that aren't being imported.
  -i, --ignore           ignore import order pre-checking.
  -v, --disableValidate  Disable cross dialogue validation of the dialogues.

See code: src\commands\import-content.js

ts list-bots [ORGID]

Lists the bots in an organisation talksuite.

USAGE
  $ ts list-bots [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-bots.js

ts list-dialogues [ORGID] [PROJECTID]

Lists the dialogues in an organisation talksuite.

USAGE
  $ ts list-dialogues [ORGID] [PROJECTID]

ARGUMENTS
  ORGID      org ID or name
  PROJECTID  org ID or name

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-dialogues.js

ts list-orgs

Lists all your organisations in talksuite.

USAGE
  $ ts list-orgs

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-orgs.js

ts list-processes [ORGID]

Lists the bots and their processes in an organisation talksuite.

USAGE
  $ ts list-processes [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-processes.js

ts list-projects [ORGID]

Lists the projects in a talksuite organisation.

USAGE
  $ ts list-projects [ORGID]

ARGUMENTS
  ORGID  org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\list-projects.js

ts login [ENV] [EMAIL] [PASSWORD]

login to talksuite to allow command line access

USAGE
  $ ts login [ENV] [EMAIL] [PASSWORD]

ARGUMENTS
  ENV       [default: produks] base url to create http calls from (only applicable for internal talksuite development)
            if you're scripting a login use produks

  EMAIL     Email that you would use to log into talksuite

  PASSWORD  password to use

See code: src\commands\login.js

ts ludown-to-luis SOURCE OUT

Convert a ludown file into a LUIS json file.

USAGE
  $ ts ludown-to-luis SOURCE OUT

ARGUMENTS
  SOURCE  source file
  OUT     output file

DESCRIPTION
  example use
  ts luis-to-ludown .\build\BotServices\luis\iTrent.json .\tmp.txt

  use the text document to add each utterance as a line
  then use something like
  ts ludown-to-luis .\tmp.txt .\build\BotServices\luis\iTrent.json
  will write it back to the luis.json
  then compare ?
  i've never done whole file though so i'm not 100 % on this
  other option would be to build a text file like:

  ## general.changeLanguage 
  - can we use pirate english 
  - can you change my lingo? 
  - can you speak like a pirate 
  - can you speak pirate 
  - change language 
  - change language of the bot 
  - change local 
  - change location 
  - change my languahae 
  - change my local 
  - change my location 
  - do you speak any other languages 
  - do you speak any other languages? 
  - how do i change my location? 
  - how do i change your dialect? 
  - how do i change your language? 
  - how do i change your local? 
  - language 

  and then convert that and manually merge that into the luis json file

See code: src\commands\ludown-to-luis.js

ts luis-to-ludown SOURCE OUT

Convert a luis json file into a ludown file.

USAGE
  $ ts luis-to-ludown SOURCE OUT

ARGUMENTS
  SOURCE  source file
  OUT     output file

See code: src\commands\luis-to-ludown.js

ts migrate-bot ORGID BOTID TEMPLATENAME

Update a Bot from a template

USAGE
  $ ts migrate-bot ORGID BOTID TEMPLATENAME

ARGUMENTS
  ORGID         org ID or name
  BOTID         bot ID or name
  TEMPLATENAME  bot ID or name

OPTIONS
  -v, --verbose  Turn on the additional log messages.

See code: src\commands\migrate-bot.js

ts update-all-processes NAME HOURS MINUTES [ORGID]

Update all processes on all bots in an org.

USAGE
  $ ts update-all-processes NAME HOURS MINUTES [ORGID]

ARGUMENTS
  NAME     The name of the process
  HOURS    The hour when the process should trigger
  MINUTES  The minute when the process should trigger
  ORGID    org ID

OPTIONS
  -j, --json  Returns in JSON format, not in a human readable form.

See code: src\commands\update-all-processes.js

ts validate-bots ORGID [BOTID]

Compare a bot against its template showing any misconfigurations and potentially performing simple fixes

USAGE
  $ ts validate-bots ORGID [BOTID]

ARGUMENTS
  ORGID  org ID or name
  BOTID  bot ID or name

OPTIONS
  -u, --update  update constants that are not valid against the templates

See code: src\commands\validate-bots.js

ts validate-content CONTENTDIR

validate local dialogues to isolate problems

USAGE
  $ ts validate-content CONTENTDIR

ARGUMENTS
  CONTENTDIR  directory to scan

See code: src\commands\validate-content.js

ts validate-project ORGID PROJECTID

Validate dialogues and languages of the specified project against global and themselves

USAGE
  $ ts validate-project ORGID PROJECTID

ARGUMENTS
  ORGID      Organisation ID that contains the project
  PROJECTID  Project ID to validate

See code: src\commands\validate-project.js

Current Tags

• 0.7.30                                ...           latest (2 months ago)

59 Versions

• 0.7.30                                ...           2 months ago
• 0.7.29                                ...           2 months ago
• 0.7.28                                ...           2 months ago
• 0.7.27                                ...           2 months ago
• 0.7.26                                ...           3 months ago
• 0.7.25                                ...           3 months ago
• 0.7.24                                ...           3 months ago
• 0.7.23                                ...           3 months ago
• 0.7.22                                ...           4 months ago
• 0.7.21                                ...           4 months ago
• 0.7.20                                ...           4 months ago
• 0.7.19                                ...           4 months ago
• 0.7.18                                ...           4 months ago
• 0.7.17                                ...           4 months ago
• 0.7.15                                ...           5 months ago
• 0.7.14                                ...           6 months ago
• 0.7.13                                ...           6 months ago
• 0.7.12                                ...           6 months ago
• 0.7.11                                ...           6 months ago
• 0.7.10                                ...           6 months ago
• 0.7.9                                ...           6 months ago
• 0.7.8                                ...           6 months ago
• 0.7.7                                ...           6 months ago
• 0.7.6                                ...           6 months ago
• 0.7.5                                ...           6 months ago
• 0.7.4                                ...           7 months ago
• 0.7.3                                ...           7 months ago
• 0.7.1                                ...           7 months ago
• 0.7.0                                ...           7 months ago
• 0.6.6                                ...           7 months ago
• 0.6.5                                ...           7 months ago
• 0.6.4                                ...           9 months ago
• 0.6.3                                ...           9 months ago
• 0.6.2                                ...           9 months ago
• 0.6.1                                ...           9 months ago
• 0.5.4                                ...           a year ago
• 0.5.0                                ...           a year ago
• 0.4.1                                ...           a year ago
• 0.4.0                                ...           a year ago
• 0.3.0                                ...           a year ago
• 0.2.36                                ...           a year ago
• 0.2.35                                ...           a year ago
• 0.2.34                                ...           a year ago
• 0.2.33                                ...           a year ago
• 0.2.32                                ...           a year ago
• 0.2.29                                ...           a year ago
• 0.2.28                                ...           a year ago
• 0.2.27                                ...           2 years ago
• 0.2.26                                ...           2 years ago
• 0.2.25                                ...           2 years ago
• 0.2.24                                ...           2 years ago
• 0.2.23                                ...           2 years ago
• 0.2.22                                ...           2 years ago
• 0.2.21                                ...           2 years ago
• 0.2.20                                ...           2 years ago
• 0.2.19                                ...           2 years ago
• 0.2.18                                ...           2 years ago
• 0.2.17                                ...           2 years ago
• 0.2.16                                ...           2 years ago