optimizely / javascript-sdk / 1434 / 7

78%

master: 78%

push

travis-ci

<a href="https://github.com/optimizely/javascript-sdk/commit/<a class=hub.com/optimizely/javascript-sdk/commit/6e008814c28a2f2a634d08d706528e5c41de181f">6e008814c<a href="https://github.com/optimizely/javascript-sdk/commit/6e008814c28a2f2a634d08d706528e5c41de181f">&quot;&gt;feat(core)[OASIS-6054]: Change Error to LOG_LEVEL.WARNING for unfound event (#418)

## Summary
- Log a warning when an event key is not found in the datafile instead of throwing an Error
- Log a warning mentioning that user tracking is not happening
- Update actual error logger in catch to be an ERROR instead of INFO
- Updated CONTRIBUTING.md instructions with CHANGELOG.md update instructions

In a similar vein as https://github.com/optimizely/java-sdk/pull/361, the JavaScript SDK noise could be more configurable for use with integrations like Segment.

_Note:_ Please pardon the prettier noise. I tried to do a prep PR in https://github.com/optimizely/javascript-sdk/pull/419 but there are still changes when I save. The actual functionality changes are in https://github.com/optimizely/javascript-sdk/pull/418/commits/</a><a class="double-link" href="https://github.com/optimizely/javascript-sdk/commit/<a class="double-link" href="https://github.com/optimizely/javascript-sdk/commit/646665d0e8275dfa07dd67153a4b78485e865715">646665d0e</a>">646665d0e</a><a href="https://github.com/optimizely/javascript-sdk/commit/6e008814c28a2f2a634d08d706528e5c41de181f">.

## Test plan
- Updated unit test to cover new functionality
- Ensure other tests pass

## Issues
- [OASIS-6054](https://optimizely.atlassian.net/browse/OASIS-6054)

662 of 739 branches covered (89.58%)

Branch coverage included in aggregate %.

7065 of 7205 relevant lines covered (98.06%)

39.27 hits per line