We’re having an issue where search results don’t show the correct path when using explicitSearchResultPath if the menu item is inside a dropdown. It only works for items directly in the menu bar.
For example, the item “REST API” in the first level menu is displayed correctly in the search result path, but items inside dropdowns are not. This makes it hard to tell results apart - for example, “Recording” appears without any context (Andoird and iOS are in SDKs Dropdown). We can’t just move everything to the top level, so we’d need a way to make the paths work properly for dropdown items too. We'd appreciate any insights or potential fixes for this issue.
You can test it live here: docs.eyeson.com

We’re having an issue where search results don’t show the correct path when using explicitSearchResultPath if the menu item is inside a dropdown. It only works for items directly in the menu bar.
For example, the item “REST API” in the first level menu is displayed correctly in the search result path, but items inside dropdowns are not. This makes it hard to tell results apart - for example, “Recording” appears without any context (Andoird and iOS are in SDKs Dropdown). We can’t just move everything to the top level, so we’d need a way to make the paths work properly for dropdown items too. We'd appreciate any insights or potential fixes for this issue.
You can test it live here: docs.eyeson.com