if true
, the corresponding resource will be excluded (when parsing path
)
if true
, runtime errors will be ignored.
if false
(or omitted) the compilation will fail with an error message
when encountering SCXML runtime errors.
NOTE: if ignored, the runtime errors will be triggered when the state-machine enters the corresponing state during runtime!
run SCXML model in "simple" or "extended" mode
optionally specify options for found resource, or specifying resources/locations directly
If input
or dialog
are missing (e.g. no resources matching them could be found),
default "minimal" state-models will be used for inputManager
and dialogManager
.
NOTE: for custom state-models whichs' files are determined by parsing StateOptions.path,
the id
will be the file name (case sensitive, without extension).
the module ID for state interpreter:
if the interpreter is registered, it can be require
'd using the moduleId
, e.g.
var stateManager = mmir.require(<moduleId>);
(the moduleId
will be automatically set for inputManager
and dialogManager
)
file path for searching (recursively) for SCXML files (state-models):
path/.../dialog.xml -> type "dialog"
/input.xml -> type "input"
NOTE: for backwards compatibility, the following file names are also accepted and mapped to their corresponding type
"dialogDescriptionSCXML.xml" -> "dialog"
"inputDescriptionSCXML.xml" -> "input"
Or custom state models (SCXML definitions) with file extension .xml
.
set or disable strict-mode for generated JavaScript code
Generated using TypeDoc
var stateOptions = { path: 'www/config/states', ignoreErrors: true, models: { input: { mode: 'simple', file: './alt_config/states_minimal/input.xml', strict: false }, dialog: { ignoreErrors: false, mode: 'extended' } } };