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] Refactor and improve Visualize Loader (#15157) #15359

Merged
merged 1 commit into from
Dec 2, 2017

Conversation

timroes
Copy link
Contributor

@timroes timroes commented Dec 1, 2017

Backports the following commits to 6.x:

* Simplify promise setup logic

* Import template from own file

* Use angular.element instead of jquery

* Add documentation for loader methods

* Add params.append

* Remove params.editorMode

* Clarify when returned promise resolves

* Add element to handler

* Allow setting CSS class via loader

* Use render-counter on visualize

* Use Angular run method to get access to Private service

* Allow adding data-attributes to the vis element

* Refactor loader to return an EmbeddedVisualizeHandler instance

* Use this.destroy for previous API

* Remove fallback then method, due to bugs

* Reject promise from withId when id not found

* Add tests

* Change developer documentation

* Revert "Use Angular run method to get access to Private service"

This reverts commit 160e47d.

* Rename parameter for more clarity

* Add more documentation about appState

* Fix broken test utils

* Use chrome to get access to Angular

* Move loader to its own folder

* Use a method instead of getter for element

* Add listeners for renderComplete events

* Use typedef to document params

* Fix documentation
@timroes timroes merged commit bead358 into elastic:6.x Dec 2, 2017
epixa added a commit that referenced this pull request Dec 2, 2017
This reverts commit bead358.

This backport was botched, so a bunch of inline diffs were committed.
@epixa epixa added the reverted label Dec 2, 2017
@epixa
Copy link
Contributor

epixa commented Dec 2, 2017

I reverted this backport because the conflicts weren't resolved properly and they all got committed.

@timroes timroes deleted the backport/6.x/pr-15157 branch December 2, 2017 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants