This fix ensures the render-complete event does not fire before rendering is actually completed.
- This ensures that the ChoroplethLayer is fully loaded, by explicitly waiting until all geojson files are loaded.
- It also removes the special init() code-path for coordinate-maps.This was the cause of coordinate-maps not showing on reports.
* 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 160e47d7709484c0478415436b3c2e8a8fc8aed3.
* 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
Reverts change in c1ef3d892f
If an error is raised before the logger is setup, then the server will exit without any notice.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* Make time picker enable/disable more granular
This makes the timefilter API more granular by removing the timefilter.enabled boolean property and introducing timefilter.enableTimeRange(), timefilter.disableTimeRange(), timefilter.enableAutoRefresh(), and timefilter.disableAutoRefresh() methods to toggle the enabled/disabled state of the time range selector and auto-refresh selector, respectively. Further, the current state of these two selectors can be read via timefilter.isTimeRangeEnabled and timefilter.isAutoRefreshEnabled.
* Clearer naming of API methods
* Reverting to !! instead of Boolean cast
* Wrapping the consequent in {} per style guide
* Removing outdated comment
* [dev/ci_setup] generalize jenkins_setup script for other CI environments
* [dev/ci_setup] accept more general `CACHE_DIR` env arg
* [dev/ci_setup] node.js install might not be invalid
* Implement getActiveInjector
* Fix typo in comments
* Rename method to sound more frightening
* Move test utils
* Add more documentation
* Fix typo in comment
* Fix name of method in comments
* input controls horizontal layout
* fix controlWidth calculation
* add functional test to ensure panel resizing changes layout
* use all caps for consts, add more comments about where values came from
* replace sleeps in functional tests with retry
* use KuiFlexGroup with wrap option instead of manually calculating widths
* remove no longer used min width constants
* Remove uiState from dashboard - communicate via the panelState instead
* migrate old app state from the url
* Add comment about migration and why the unused uiStateJSON field is kept around still
* Add url whitelist
* Use .some
* Add/fix tests
* Add browser tests
* Initial pass
* Different approach, and more tests
* Fix linting issues
* Special case relative urls starting with `#`
* Handle root relative link too
* Try this another way
* Reapply my changes
* allows to hide warnings in gauge
* should default to true if option is not set
* fixing based on review
* default for isDisplayWarning needs to be applied, else it fails
* Fix IE11 bug which caused kuiToolBarSearch to grow too wide when there is only a single kuiToolBarSection sibling.
* Fix bugs with KuiListingTableToolBar rendering empty sections. Update docs example to demonstrate a tool bar with a search and a section.
In 7.0 ES put a limit on the number of fields that a query can expand to. Since a search term without an explicit field selection hits all fields by default, a kibana user could get an error if the index they're searching against has more than 1024 fields. With lucene, the ES admin could fix this by changing the default_field in their index settings. Kuery still had a problem though, because multi_match did not support default_field. The ES team kindly added default_field support to multi_match for us, so this PR updates Kuery to rely on default_field when a user submits a query without an explicit field.
* get wiring done for timelion application functional tests
* add tests for expression type ahead functions, arguments, and argument values
* provide argument suggestions when argument name not provided
* updates from cjcenizal review
* [Logging] more tests and added robustness to log formatting
* empty string for default error message, along with TODO question comment
* try to use stack trace from error when there is no error message
* simplify using the stack as the default error message
* destructure get from lodash
* default no-message to static string instead of error stack
* fix tests
