-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GS] Add Dev Tools deep links to navigational search #86172
Comments
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
@cjcenizal Any updates on when this might be possible? |
@joshdover In theory it's possible we might be able to squeeze this into 7.13, but we have a number of high priority projects on our roadmap that already occupy our full team capacity so it seems unlikely. The earliest empty slot on our roadmap is in 7.15. |
@cjcenizal Thanks for the update! I really hope this wouldn't take more than a couple of days and I'm happy to help however I can. |
This has been mostly solved by #96135 except for the Painless Lab case. This one needs to be worked a bit separately because it doesn't currently provide a plain string representation of the app's title to the dev_tools plugin. |
Closing this issue as most of the work has been completed. We can open up a separate issue for Painless Lab, if needed. |
Meta issue: #72680
In #83380 we added support for applications to include a
searchDeepLinks
property on theircore.application.register
call which feeds into the navigational search feature.Dev Tools should add this property to add deep links for their key locations to search. In most cases, this should be adding an array with the name of the location and a URL path to the route in your app. See the documentation for this API for more info. Some things to consider:
title
for each link should be localizedpath
for each link should be relative to your application'sappRoute
. Base path does not need to be included.appUpdater$
API. See the example in the Stack Management app.New links to add
Dev tools
The text was updated successfully, but these errors were encountered: