Skip to content
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

[6.x] [new-platform] migrate ui/chrome/loading_count API to new platform (#21967) #22156

Merged
merged 1 commit into from
Aug 18, 2018

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Aug 17, 2018

Backports the following commits to 6.x:

…lastic#21967)

Part of elastic#20696, required for elastic#20697

This migrates the `chrome.loadingCount` API to the new platform, which was not planned to happen before elastic#20697 but is required as the UiSettingsClient uses the loading count to activate the global loading indicator in Kibana. This service is pretty simple, it allows adding an observable with `core.loadingCount.add(observable)` that will be subscribed to in order to contribute to the current "loading count", which can be retrieved with `core.loadingCount.get$()`.

The `ui/chrome/api/loading_count` module is taking the start contract from the service and re-exposing it via the existing `chrome.loadingCount` api that we have today, including `increment()`, `decrement()`, `subscribe()`, and the automatic watching of the loading count exposed by the angular `$http` service.
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@spalger spalger merged commit fad921d into elastic:6.x Aug 18, 2018
@spalger spalger deleted the backport/6.x/pr-21967 branch August 18, 2018 05:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants