-
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
[APM] Use platform history object #65682
Labels
Team:APM - DEPRECATED
Use Team:obs-ux-infra_services.
technical debt
Improvement of the software architecture and operational architecture
v7.10.0
Comments
Pinging @elastic/apm-ui (Team:apm) |
#63443 makes it so links to Discover and Home (tutorials) don't cause a full refresh. That PR fixed the links to make them use the correct locations, but still cause a full refresh because we're not using the above or the |
#65164 may allow us to have more links work without the router changes or having to use |
Thanks Nathan, that sounds awesome
Op vr 8 mei 2020 21:53 schreef Nathan L Smith <[email protected]>:
… #65164 <#65164> may allow us to
have more links work without the router changes or having to use
navigateToApp.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#65682 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACWDXAOS2WKUR4BHL3HX6LRQRPLTANCNFSM4M3KVKNA>
.
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Team:APM - DEPRECATED
Use Team:obs-ux-infra_services.
technical debt
Improvement of the software architecture and operational architecture
v7.10.0
We are currently using a hash-based
history
object. However, in NP, Platform injects its own (HTML5-based)history
object that we should use. This would allow us to get rid of hash-based routing and create less friction when navigating between different Kibana plugins/apps.See #64804, which was addressed with a temporary workaround
Related: #51963
The text was updated successfully, but these errors were encountered: