-
Notifications
You must be signed in to change notification settings - Fork 68
wire debug
Brian Cavalier edited this page Aug 30, 2011
·
3 revisions
The wire/debug
plugin outputs diagnostic information to the console as wire specs are wired as well as when contexts are destroyed.
It tracks components as they pass through the lifecycle, and outputs information as each component reaches the ready state. In verbose mode (see Options below), it will output information for each step in the lifecycle for each component (extremely verbose!). If a component cannot reach the ready state for any reason (e.g., it requires an unresolvable reference), wire/debug
will output error information to the console.
In general, wire/debug
makes the wiring process louder to help you track down problems that cause wiring to fail.
NOTE: You should not use the wire/debug
plugin in production
{
module: 'wire/debug',
// verbose
// If set to true, even more (a LOT) info will be output.
// Default is false if not specified.
verbose: false,
// timeout
// Milliseconds to wait for wiring to finish before reporting
// failed components. There may be failures caused by 3rd party
// wire plugins and components that wire.js cannot detect. This
// provides a last ditch way to try to report those failures.
// Default is 5000ms (5 seconds)
timeout: 5000,
// filter
// String or RegExp to match against a component's name. Only
// components whose path matches will be reported in the debug
// diagnostic output.
// All components will still be tracked for failures.
// This can be useful in reducing the amount of diagnostic output and
// focusing it on specific components.
// Defaults to matching all components
// Examples:
// filter: ".*View"
// filter: /.*View/
// filter: "[fF]oo[bB]ar"
filter: ".*"
}