DropdownV2 downshift memory leak

Detailed description

This applies to any component using downshift.

If the component (specifically DropdownV2 in my case) is focused, when the component is unmounted and dismissed after the submit, in a modal for example, react warns Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application.

Steps to reproduce the issue

1. Display a modal with DropdownV2
2. Select an option in the dropdown
3. While the dropdown is still in focus, click the primary button submit in the modal
4. This will close the modal and display the memory error (only if the component is in focus when submitting)

Additional information

This seems to have been a known error and solved in version 2.0.7 of downshift. Currently carbon-components-react seems to have ^1.31.14 as the downshift dependency version. https://github.com/downshift-js/downshift/issues/476

[joshblack]

@dakahn we will need to bump to v3 of downshift, I believe, if we want to keep using it 👍 I believe they have migration guides to help us out here too

[carbon-bot]

Hi there! 👋 If you’re wondering why this issue was moved, we’re currently updating our repo structure so that every package is found in the same project.

This should not have any impact for you, but we wanted to give you a heads up in case you were wondering what is going on. If you have any questions, feel free to reach out to us on Slack or contact us at: [e-mail]. Thanks!