Closed demurgos closed 5 years ago
The CI failure seems to be an Appveyor issue (issue in their npm
package). Fixed in https://github.com/tapjs/foreground-child/pull/24.
This also fixes a bug: https://github.com/tapjs/foreground-child/pull/30#issuecomment-422700978
@demurgos this seems reasonable to me, do we have tests already for each function signature?
@bcoe See #30
Why
foregroundChild
has a complex signature. Using a dedicated function for arguments normalization would improve clarity.What
Document the signature of
foregroundChild
, move arguments normalization to a separate function, small simplification to the normalization.