* [npm] upgrade babel
The upgrade to babel 6 requires an upgrade to all of the associated modules, which meant that a few other things changed at the same time. The most notable is the way that we handle our babel-options, which is now done with an npm module and includes using the babel-loader's "presets" query string param.
This meant changes to the babel_options.js module and extending it to help setting up the "babel-register" module, which was previously copy-pasted in several places.
* [mtodules] upgrade to support babel6 module semantics
* [eslint] fix lint errors
* [babel] ignoer massive fixture files
* [cli/errors] use Object.setPrototypeOf since subclassing Error is broken
* [babel] Upgrading core babel libraries
[babel] Use WIP babel-6-fix branch of babel-preset-kibana
* Fix broken test
* [babel] Reverse unnecessary module.exports changes
* Fix notifier
* Use babel presets and plugins directly
* [babel/options] resolve preset/plugins paths for better plugin compatibility
* [babel/options] use babel-preset-env for correct node settings
* [babel] cache babel compilation in webpack like we thought we were
* defer loading visualization saved objects so they can be loaded in a single _mget
* Don't request field stats more than once for the same index pattern
* [ui/courier] batch fetch requests for all searches and docs
* [ui/courier] remove remaining mentions of req.isFetchRequested()
* [courier/fetch/request] remove unneceessary !!
* Add a sleep to Header page object's clickTimepicker method, to wait for the page to render on Jenkins.
* Add a sleep to Visualize page object's clickNewSearch method, to wait for the page to render on Jenkins.
* Wait for loading indicator to disappear to signify completion of clickNewSearch() in Visualize page object.
* Wrapper Header page object's clickTimepicker method in a try block.
* Refactor Visualize Wizard to use explicit controller names, instead of defining them dynamically.
* Add landing page with table to Visualize app.
* Update Visualize wizard UI.
* Add kuiIcon--basic and support icons in Table component. Display icons in Visualize landing page.
* Refactor Visualize Wizard templates to use import syntax.
* Set kuiViewContent width to 100% to avoid it shrink wrapping its content.
* Move ToolBar buttons to the right side. Remove labels and add tooltips.
* Remove unused Visualize load menu template.
* Disable timepicker in Visualization listing.
* Change Visualize route names. Add omitPages attribute to breadcrumbs directive. Make Visualize breadcrumbs into links.
* Remove Open and New menu buttons from Visualize.
* Add ConfirmationModal for deleting visualizations.
* Implement sorting for name and type columns in Visualize listing.
* Refactor Visualize routes into VisualizeConstants file. Fix functional tests.
* Add pager_controls directive and pager service. Add pagination to Dashboard and Visualize landing pages. Change Dashboard listing to use hrefs for each dashboard.
* Use ng-if instead of ng-hide to hide/reveal Table action buttons in Dashboard listing.
* Redirect from old Visualize wizard routes to new ones.
* Use ViewContent and Title components in Visualize wizard.
* Fix Visualize and Dashboard listing table logic so that selection only applies to the current page of items.
* Paging clears the selection.
* Searching clears the selection.
* Sorting clears the selection.
* Use consistent "Create" terminology in both Visualize and Dashboard for creating new items.
* Use NoItems and PromptForItems components in Visualize listing view.
* Use $injector to inject dependencies in Visualize and Dashboard listing.
* add architecture styleguide
* be clearer about application architecture
* define as plugin architecture
and downplay the webpack alias and shims that are available
* fix typo, simplify server description
* Avoid mget calls for every visualization after panel collapse
This will still cause the data to refresh (an msearch call).
* use ng-hide check, not width check
* Add all_fields to highlight query to improve highlighting
* Refactor highlighting and move out of _flatten
* Make changes as per @bargs' requests
* Add documentation about highlightAll setting
* Fix docs typo
* Remove unused function
* Remove unused code
* Fix an empty data table visualization scenario
In ui/agg_response/ we parse the ES response. For each value we create
an AggConfigResult object, and its quite normal to pass nulls as a value
into it.
It is a bit harder to cause in a data table visualization, but it is
possible with a large data set and many metric and bucket aggregations.
If an aggregation result is a null, it broke the data table
visualization, because Angular didn't know how to handle it for sorting.
* undo changes to AggConfigResult initialization
* fix AggConfigResult null value in paginated table valueGetter
* Adding initial autocomplete rules for Ingest APIs
* Fixing append processor autocomplete rules
* Adding autocomplete rules for Convert processor
* Adding autocomplete rules for the Date processor
* Adding references to docs
* Adding autocomplete rules for Date Index Name processor
* AAdding autocomplete rules for the Fail processor
* Adding autocomplete rules for Foreach processor
* Adding autocomplete rules for Grok processor
* Adding autocomplete rules for gsub processor
* Fixing autocomplete rules for Gsub processor
* Adding autocomplete rules for the Join processor
* Adding autocomplete rules for JSON processor
* Adding autocomplete rules for the KV processor
* Adding autocomplete rules for Lowercase processor
* Adding autocomplete rules for the Remove processor
* Adding autocomplete rules for the Rename processor
* Adding autocomplete rules for the Script processor
* Adding autocomplete rules for the Set processor
* Adding autocomplete rules for the Split processor
* Adding autcomplete rules for the Sort processor
* Fixing definition of Sort processor
* Adding autocomplete rules for the Trim processor
* Adding autocomplete rules for the Uppercase processor
* Adding autocomplete rules for Dot Expander processor
* Fixing autocomplete rules for Dot Expander processor
* Fixing forward reference problem
* Removing TODO note
* Enable (recursive) autocomplete on foreach processor's "processor" field
* Dashboard clean up
- Stop storing the grid element on the panel which caused a circular
reference and required special code to make it serializable.
- Call state.save directly rather than broadcasting change:vis
This is in prep for possibly making grid scope isolate and view/edit
mode implementation.
* Make dashboard grid scope isolate
This will help prepare for state changes for view/edit mode in
dashboard.js
* Remove unnecessary uses of findPanelByPanelIndex
can just use the panelElement directly
* Only need the panelIndex stored on the inner element
* Remove memory leak
Clean up panelElementMapping
Adds + and - icons on hover in the doc table and data table, allowing users to drill down with more options and fewer clicks. Previously in the doc table a user had to expand the row in order to filter on a document value. In the data table a user could filter simply by clicking a cell, but there was no way to create a negative filter. This commit brings feature parity between the data table and doc table.
The custom debounce implementation uses Angular's `$timeout`, which
interacts unfavourably with the unconditional `$watch` handler used in
the `fixed-scroll` directive. It results in an infinite digest being
triggered about every 100ms. To avoid that, this commit uses the
`invokeApply` option of `$timeout` and instead calls `$scope.$apply`
conditionally.
* Reordering fields to closely follow previous field choices
* Moving deprecated choice field to end of form.
* Forgot to move related section
* Always show "Time-field name" field when index is time-based
* Only require the field when it's not disabled
* Add inactive and info Icons.
* Add info, success, and warning InfoPanels. Change background-color to white and use a colored border instead.
* Update Saved Object Management view to use new InfoPanel styles.
* Address Shaunak's feedback.
* Add ability to pass a title and show the close button on a modal
* address code review comments
- Clean up tests and add some new ones
- Default onClose to onCancel if nothing is supplied.
* Switch to absolute mode when using timepicker step forward/backward buttons
* Instead of merging state, replace entire time object
* Uncomment time navigation buttons and fix pretty duration
Rather than wrapping two discrete webdriver requests in a single try()
block, we do each request in its own block to help prevent inconsistent
failures.
* Introduce dashboard landing page
Still TODO:
- Add clickable breadcrumbs
- Remove New and Open top nav options
* use clickable breadcrumbs instead of 'New' and 'Open' nav items
* code cleanup
improve tests
* Add new empty dashboard styling
* Fix selenium tests
* Address code review comments
- rename bread_crumb_url => bread_crumb_urls
- fix reporting link in dash (separate PR)
- Use NoItems instead of PromptForItems when searching
- Style fixes
* Use a constant for the landing page url
* Fix tests
For consistency sake all Kibana plugins should probably handle ES errors the same way. We could achieve this by exposing the handleEsError function that is already defined in the core Kibana plugin.
* Use better confirm button text. rename safe confirm.
Use confirm_modal_promise only when it’s easier than using
confirm_modal directly.
change all native confirmations to the new dialog
* address code review comments
* Be consistent with the confirm button text pattern
Address other code review comments
* remove default option for confirmButtonText
Require onConfirm and confirmButtonText for confirmModal
* fix tests for no longer using alertText
* address code review comments Round 2
* Document TextArea component and remove classes from base.less.
* Move StaticInput component into the UI Framework and remove classes from base.less.
* Remove kuiInput class by merging it into kuiSideBarInput class.
* Improve VerticalRhythm documentation.
