forked from OpenNeo/impress
Sentry issue IMPRESS-2020-20 doesn't have a clear backtrace, but it looks like the usual thing where we trigger an Apollo query directly, and forget to catch a potential error in the returned promise. I noticed that the last thing the user did was type in the search bar, and got a _caught_ error for the initial search! Scanning the SearchPanel file, I think it's likely that this was a failure in `fetchMore` for the infinite pagination. I'm a bit worried as to _why_ we were doing infinite scrolling stuff when there were no results? I wasn't able to repro a scroll event on the empty results list, but it's plausible that it could happen. I've added a gate to not send this request when there's an error! |
||
|---|---|---|
| .. | ||
| support | ||
| index.js | ||
| Item.js | ||
| ItemsAndSearchPanels.js | ||
| ItemsPanel.js | ||
| OutfitControls.js | ||
| PosePicker.js | ||
| SearchPanel.js | ||
| SearchToolbar.js | ||
| useOutfitState.js | ||
| WardrobeDevHacks.js | ||
| WardrobeOutfitPreview.js | ||
| WardrobePageLayout.js | ||