Fix issues with facet values count update #466
Merged
Conversation
This file contains 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
dms1lva
approved these changes
May 17, 2017
test/ui/FacetValuesTest.ts
Outdated
| expect(oldValues.get('@token9').occurrences).toEqual(10); | ||
| }); | ||
|
|
||
| it('should set occurrences to 0 in old values if a new values does not exist in old values', ()=> { |
There was a problem hiding this comment.
I think you meant "should set occurences to 10". Also, "if a new value".
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.
We only need to return a zero occurrences when merging two list of facet values when the old list has no occurences, otherwise we should keep the old count.