As mentioned in the discussion on #82870, some of the link components in shared/Links/apm/ are no longer being used, but hooks that call useAPMHref now being used and are contained in those files in order to keep logic for constructing links located together.
In general, having components that render wrapped EuiLink components can be less useful, as demonstrated by the PR mentioned above: Using an EuiLink inside of an EuiTab causes problems with keyboard focus. EuiTab takes an href prop, which is the only thing we need.
The links and hooks are differentiated by which filters need to be persisted between navigation, so it still makes sense to have different hooks for different locations.
We could possibly make one hooks file that exports multiple hooks and replace the use of the link components.
As mentioned in the discussion on #82870, some of the link components in shared/Links/apm/ are no longer being used, but hooks that call
useAPMHrefnow being used and are contained in those files in order to keep logic for constructing links located together.In general, having components that render wrapped
EuiLinkcomponents can be less useful, as demonstrated by the PR mentioned above: Using anEuiLinkinside of anEuiTabcauses problems with keyboard focus.EuiTabtakes anhrefprop, which is the only thing we need.The links and hooks are differentiated by which filters need to be persisted between navigation, so it still makes sense to have different hooks for different locations.
We could possibly make one hooks file that exports multiple hooks and replace the use of the link components.