Conversation
Bundle Size ComparisonFull build detailsThe full bundle is smaller than main by -0.14 kB. 🎉 The index.js is larger than main by 0.01 kB. ❗ Run
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2081 +/- ##
==========================================
- Coverage 95.85% 95.84% -0.02%
==========================================
Files 756 756
Lines 17773 17776 +3
Branches 4978 4978
==========================================
+ Hits 17037 17038 +1
- Misses 684 686 +2
Partials 52 52 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
| if ( | ||
| collectionId === zustandState.granules.granules.collectionConceptId | ||
| && !isOpenSearch | ||
| !collectionId |
There was a problem hiding this comment.
Should we put this catch further up if (!collectionId) return on something like line 49? if the coll is empty do we need to execute anything else on this slice instead bail?
There was a problem hiding this comment.
I originally had it further up but I was looking at what was triggering it, and the bug is because of the opensearch double trigger mentioned in the comments. So I moved it into this if statement. I meant to add details to that comment, I'll do that now
…es timeout for moving map to shapefile after the projection changes
Overview
What is the feature?
Fixes granules requests with no collection concept id. When getGranules is called with no collectionConceptId, return without fetching granules because that is an invalid request to CMR
Additionally I think I fixed the playwright flakiness. I blocked tophat from loading in playwright tests, and I ensured that the tophat container remained the same size. After that I made a few other minor playwright changes and retook every screenshot. I got two runs in a row with no failures.
What areas of the application does this impact?
Granules
Testing
Reproduction steps
From the collection results page, click on a collection to view granules (or to view collection details), then immediate press the back button (either browser back or "Search Results (# Collections)" link.
Ensure that the red error banner is not displayed
Checklist
npm audit fixand made note of any changes in this PR