Add debounce to fetch results when conditions change

[marySalvi]

Closes #1034
Adding a debouce to fetchResults when conditions change ensures that the desired query when copying a url is fired second and eliminates the race condition.

[naglepuff]

I'm still seeing 2 requests on reload. (http://localhost:8081/?q=ChsIABACGAIiEyJNZXRhdHJhbnNjcmlwdG9tZSIKHwgAEAAYASIXIktFR0cuT1JUSE9MT0dZOkswMDI5MiI=)

This is likely because the fetchResults call on line 59 (outside of the watcher) is not debounced.

I think creating a debounced version of fetchResults and using it in both places would do the trick.

[marySalvi]

I'm still seeing 2 requests on reload. (http://localhost:8081/?q=ChsIABACGAIiEyJNZXRhdHJhbnNjcmlwdG9tZSIKHwgAEAAYASIXIktFR0cuT1JUSE9MT0dZOkswMDI5MiI=)

This is likely because the fetchResults call on line 59 (outside of the watcher) is not debounced.

I think creating a debounced version of fetchResults and using it in both places would do the trick.

Good call. Fixed in e1d41fa

[naglepuff]

LGTM!

I used the network tab in devtools to verify that only:

• 1 call was made to /api/biosample/search
• 2 calls were made to /api/study/search (1 for studies, 1 for consortia),

Where before 2 and 4 calls were made respectively.

I also checked http://localhost:8081/users and http://localhost:8081/submission/home to make sure that the results weren't suppressed (which was the reason the original fix for this problem had to be rolled back).