silvermine / lambda-express

99%

master: 99%

Pull #47

travis-ci-com

fix: Add a safeguard for JS users when setting response headers

We aren't adding many JS safeguards since we're providing type safety by
means of TypeScript. However, in this case, many users could easily have
been thrown off by trying to set response headers with non-string values
(e.g. booleans and numbers). Rather than a) failing silently, or b)
trying to convert those values for them, guessing at how they want them
converted, we will instead log an error to warn the developer of the
mistake.

229 of 231 branches covered (99.13%)

Branch coverage included in aggregate %.

1 of 1 new or added line in 1 file covered. (100.0%)

467 of 469 relevant lines covered (99.57%)

1742.39 hits per line