Don't require all keys to be configured to enable key checks (#2816) #2941
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Should fix #2816 |
steven-supersolid
changed the title
flovilmart
reviewed
Oct 26, 2016
|
|
||
| // All keys mismatch | ||
| if (keyMismatch == keys.length) { | ||
| var oneKeyConfigured = keys.some(function(key) { |
|
@steven-supersolid updated the pull request - view changes |
|
Thanks!! :) |
flovilmart
approved these changes
Oct 26, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a few tests to try to be descriptive about how we expect keys to behave.
Tried to make the key checking algorithm clear - could be optimised by looping just once but we are only iterating up to 4 times.