Configuration for mmir modules (analogous to requirejs' module config entries)
Specify additional (mmir) runtime configuration values,
e.g. in addition to config/configuration.json.
In case of conflicts, these settings will override settings in
config/configuration.json,
Specify how (mmir) controller implementations should be parsed/included, and/or specify additional controllers that should be included.
If false, (mmir) controllers will be excluded/ignored.
disable logging in mmir runtime: suppresses all logging-output by replacing mmirf/logger with an empty logger implementation
HACK:
webpack version 4 does include a default rule for loading WASM files
that will cause errors due to the fact, that it will try to load mmir-integrated WASM files again.
Enabling this option will overwrite the webpackConfig.module.defaultRules option omitting the
default rule for WASM files.
If you do not need the default rules, this can be enabled as a quick-fix for dealing with errors due to loading WASM files.
Specify how (JSON) grammars should be parsed/included, and/or specify additional grammars that should be included.
Compiled grammars will be available via the SemanticInterpreter.
If false, grammars will be excluded/ignored.
Specify how (mmir) helper implementations (for mmir controllers) should be parsed/included, and/or specify additional helpers that should be included.
If false, helpers will be excluded/ignored.
include a (optional) module, e.g. will be available via
mmir.require().
The prefix "mmirf/" can be omitted.
Specify and configure mmir-plugins that should be included.
If jquery is included:
mmir will automatically use jquery utililities instead of alternative
implementations.
NOTE: the jquery library must be loaded/included separately; this will
only configure mmir to use jquery, but not include the library itself.
include module AND do load it AFTER initializing the mmir library;
the module will also be available via mmir.require().
The prefix "mmirf/" can be omitted.
include module AND do load it BEFORE initializing the mmir library;
the module will also be available via mmir.require().
The prefix "mmirf/" can be omitted.
Specify how (mmir) data model implementations should be parsed/included, and/or specify additional data models that should be included.
If false, data models will be excluded/ignored.
specifying additional (or replacing) module paths
specify the path to the MMIR resources directory with the default structure:
config/
/languages/
/<lang>/
/grammar.json
/dictionary.json
/speech.json
/states/
/input.xml
/dialog.xml
/configuration.json
controllers/*
helpers/*
models/*
views/*
The path will be used to collect all available resources and create the correspondig options for including them.
used for resolving non-absolute paths: the absolute path to the app's root/sources directory (if omitted the current working directory is used for resolving non-absolute paths)
(for internal use: will be filled/set by compiler)
dictionary for mmir runtime settings:
"mmirf/settings/configuration": the (normalized/merged) RuntimeConfiguration for the mmir app (~ configuration.json)"mmirf/settings/directories": the directories/files/URI information for loading/accessing speech-configuration, controllers, views etc. (~ directories.json)"mmirf/settings/speech/{lang}": the speech (input/output) configuration for language code lang (~ lang/speech.json)"mmirf/settings/dictionary/{lang}": the dictionary (internat. labels) for language code lang (~ lang/dictionary.json)"mmirf/settings/grammar/{lang}": the JSON definition for the grammar of language code lang (~ lang/grammar.json)Specify how (mmir) configuration and settings should be parsed/included, and/or specify additional settings that should be included.
The mmir configuration/settings are the resources that are by default
located in the mmir config/ directory
(with exception of the states sub-directory; for those instead use WebpackAppConfig.states):
config/
/languages/
/<lang>/
/grammar.json
/dictionary.json
/speech.json
/states/
/input.xml
/dialog.xml
/configuration.json
(NOTE the config/states/ sub-directory is handled/configured via the the states option)
Specify how (SCXML) state-machines/-models should be parsed/included, and/or specify additional state-models that should be included.
If false, state-models will be excluded/ignored.
By default, if no state-models are include, "minimal" state-models for the InputManager and the DialogManager will be included, see mmir-tooling/defaultValues.
Specify how (mmir) views should be parsed/included, and/or specify additional views that should be included.
If false, views will be excluded/ignored.
configuration for webpack plugins (for internal use)
Generated using TypeDoc
var appConfig = { //path to directory that contains classic mmir directory structure resourcesPath: 'src/mmir', resourcesPathOptions: { //for included models, controllers, helpers: convert old-style // implementations by adding an export statement addModuleExport: true, //exlude model implementations, and do not include JSON grammar resources exclude: ['models', 'settings/grammar'] }, //utilize jQuery in mmir instead of (less backwards compatible) // alternative implementations (npm package jquery needs to be installed!) jquery: true, //specify language for runtime configuration (== configuration.json) configuration: {language: 'en'}, //do include controller implementation found within resourcesPath // (NOTE: this is the default behavior) controllers: true, //do NOT include helper implemenations found within resourcesPath helpers: false, //... }