This PR fixes hotkey escape on advanced filter dropdown, which wasn't working. It adds a parameters to openDropdown, because in this particular case, the dropdown is not opened from its clickable component but from an openDropdown, in that case it wasn't possible for openDropdown to know which hotkey scope to take, because the hotkey scope is generally passed in the Dropdown component props. We might want to find a more robust solution, where a dropdown knows its hotkey scope without having to be mounted. --------- Co-authored-by: Raphaël Bosi <71827178+bosiraphael@users.noreply.github.com>
Run yarn dev while server running on port 3000