Closed julienw closed 4 months ago
Name | Link |
---|---|
Latest commit | a5898c5987276ba0ad369c281248cf10c3598adf |
Latest deploy log | https://app.netlify.com/sites/mozilla-perfcompare/deploys/6662c5084f07420008cb9241 |
Deploy Preview | https://deploy-preview-671--mozilla-perfcompare.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Attention: Patch coverage is 94.73684%
with 2 lines
in your changes missing coverage. Please review.
Project coverage is 91.80%. Comparing base (
1f9f726
) to head (67b42a6
).:exclamation: Current head 67b42a6 differs from pull request most recent head a5898c5
Please upload reports for the commit a5898c5 to get more accurate results.
Files | Patch % | Lines |
---|---|---|
src/components/Search/SearchInputAndResults.tsx | 94.73% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
There was 2 issues:
This first commit fixes both issues, by using useCallback and incrementing the search id in the right place.
The second commit is a small correctness issue where
handleEscKeypress
wasn't memoized. I think it wasn't doing any problem but it's more consistent with the other functionhandleDocumentMousedown
.Finally the 3rd commit fixes a bunch of issues with the existing test for the SearchView. The biggest issue (IMO) is that the mock was always returning all the data, because it wasn't configured in the correct order. I thought the library would order it by specificity but it's not doing it.