I noticed that the DataBrowser was sending duplicative XHRs, which I found out was resulting from the asyncComputed getter being fired multiple times even though the values hadn't changed. After fighting with asyncComputed for about 2 hours, I gave up on it and just did it the normal, more procedural way and everything worked fine.
This also fixes an issue of too-aggressively refreshing based on the pagination options watch.
I noticed that the DataBrowser was sending duplicative XHRs, which I found out was resulting from the asyncComputed getter being fired multiple times even though the values hadn't changed. After fighting with asyncComputed for about 2 hours, I gave up on it and just did it the normal, more procedural way and everything worked fine.
This also fixes an issue of too-aggressively refreshing based on the pagination options watch.