Just saw a duplicate key error in the HearingsScheduled carousel when poking around the site locally. It looks like we're just using the id of the underlying event for the key, but we have different types of events pulled from different sources that can (and in at least one case this month, did) have the same key. Adding type to the key here should guarantee the key's uniqueness going forward.
Checklist
[na] On the frontend, I've made my strings translate-able.
[na] If I've added shared components, I've added a storybook story.
[na] I've made pages responsive and look good on mobile.
Summary
Just saw a duplicate key error in the
HearingsScheduled
carousel when poking around the site locally. It looks like we're just using the id of the underlying event for the key, but we have different types of events pulled from different sources that can (and in at least one case this month, did) have the same key. Adding type to the key here should guarantee the key's uniqueness going forward.Checklist
Screenshots
N/A
Known issues
N/A
Steps to test/reproduce