Closed theredpea closed 4 years ago
Not sure if intentional, may be "working as designed" daemon.js abortOnError argument checks for instanceof Boolean,
abortOnError
This means if I pass abortOnError : true (primitive true), the daemon will interpret and run with the argument false!
true
false
If it helps I can make pull request to do either of these:
instanceof
config.abortOnError === true ? config.abortOnError : false
(this.abortOnError==true?'y':'n'),
an attribute called abortOnError can be set to true...
an attribute called abortOnError can be set to new Boolean(true)...
new Boolean(true)
Yeah, that was a kludgy implementation. It's updated in master.
Not sure if intentional, may be "working as designed" daemon.js
abortOnError
argument checks for instanceof Boolean,This means if I pass abortOnError : true (primitive
true
), the daemon will interpret and run with the argumentfalse
!If it helps I can make pull request to do either of these:
instanceof
config.abortOnError === true ? config.abortOnError : false
(this.abortOnError==true?'y':'n'),