v1.2.8

Enabling logging {logging: true} on a child thread will override the console.

Both the Child and The Parent support a common log system. A child thread with the option {logging: true} activated (on itself) will report console.info(), console.log(), console.warn(), and console.debug(). The console will be overridden and yet still report issues during debug mode.

The parent thread or thread manager will control whether or not both the log messages from the child and the internal debugging messages from @jumpcutking/Threads itself.

The options {verbose: true, logging: true} on the parent thread manager init help toggle the amount of logging. Verbose activates detailed logs about the internal workings of the Thread Manager; this can be very helpful when creating a process to work with threads that are not written in a supported program language. Logging will activate the specific action that a child's thread will report or deactivate so that only the parent thread's specific console is revealed.

Hush has been replaced with logging. Activate {logging: true} on both the Thread manager and the child.

Thread children can now have console.log overridden to report logs directly to the parent thread.

Logs are now a little prettier, and reading the information from the console is easier.

Verbose mode is now activated on init().

Bug fixes and resolutions.

Full Changelog: v1.2.6...v1.2.8