Apparently, the mutation service was using a JS promise instead of using $q to create a promise. Therefore scope was not being applied/updated to set isSearching to false even though search results had been returned.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Functional tests
UI doesn't get stuck searching after results have already been returned
Issue Number
Closes #162
Purpose/Implementation Notes
Apparently, the mutation service was using a JS promise instead of using
$q
to create a promise. Therefore scope was not being applied/updated to setisSearching
tofalse
even though search results had been returned.Types of changes
What types of changes does your code introduce? Put an
x
in the boxes that applyFunctional tests