* [webpack] upgrade to @elastic/webpack-directory-name-as-main v2
* bump @elastic/webpack-directory-name-as-main
* import browser mocha with webpackShim
`import 'mocha'` will resolve to `mocha/index.js`, which points to
`mocha/lib/mocha.js`, the node version of mocha. This will not work in
the browser.
Since ng_mock is browser code, we need the mocha build for the browser,
which lives at `mocha/mocha.js`. This isn't referenced at all in the
package.json file, but is references in the bower.json file. Webpack,
however, doesn't observe the bower config, so we need to specifically
reach into the mocha package and point to the `mocha/mocha.js` file.
Switching between tabs in the spy panel takes a really long time in the
Discover histogram. The root cause is that there is an expensive forced
layout happening. It's expensive because the "response" tab includes all
500 hits from the search response which is a lot of content. This
affects all the tabs because we're using ng-show instead of ng-if,
meaning we're incurring the cost of layout on all that content even when
it's not being shown. This PR switches to ng-if to speed up all of the
tabs other than "Response".
The response tab remains slow because the vis is re-rendered any time
uiState changes, and when the vis is re-rendered it triggers forced
reflows. This is a non-trivial issue to fix that Peter is already
working on separately, so for now we'll settle for only speeding up the
other tabs.
Fixes https://github.com/elastic/kibana/issues/9464
* Componentize Saved Objects table.
* Remove inline Buttons from Table. Add MicroButtons to serve the same purpose.
* Use fat arrow function instead of self var in _objects.js. Add 'areAllRowsChecked' controller method. Add TODO comments to migrate scope vars to the controller.
Webpack v1 checks for the exact package name as the given loader name
before adding the -loader suffix, which is what we really want.
Unfortunately, this can mean that webpack can accidentally pick up
non-webpacker loader modules if they are at the top level of the
dependency graph, which is far more likely in npm 3+.
Webpack v2 will require all loaders to be explicitly named with the
-loader suffix (where appropriate), so this change gets us closer to
that anyway. See https://github.com/webpack/webpack/pull/3102
* [WIP] new scripted field tests
* Final improvements on 12 new tests for 1 expression and 2 painless scripted fields
* Add try loops around testing first Discover doc
* Set timezone to UTC and adjusted data accordingly
* Added boolean and date Painless scripted field types
* Remove unused (non-working) methods
* Fix lint error
* Added several data-test-subj attributes and used them in the tests
* Reverting previous change to getBarChartData
* Refactor code that loads saved objects
* couple fixes and comments
cleanup & comments
cleanup
* Use es6 classes, make a note about getting rid of the 100 hard limit on results
* Address comments
* fix linter
* lint fixes with { } spacing
* Fix linter
* fix forgotten merge conflict
* and linter
PhantomJS is using a rather outdated version of WebKit, which requires
various css-prefixes to render correctly. PhantomJS doesn't have a specific
user-agent, and Safari 7 is the closet version of WebKit.
* [grunt/eslint] fix precommit linting
- remove use of `minimatch.makeRe()` because it does not support the entire glob syntax
- log a warning whenever a js file is excluded by the `lintStagedFiles` task
- eslint globs are relative to the project root, ensure that we check against relative version
* [grunt/eslint] only log warning wtr grunt paths
- Icon, Link, Button, TextInput, CheckBox, Table, ControlledTable, ToolBar, ToolBarFooter.
- Update Local Nav to use classes with kui prefix.
- Add PostCSS loader to UI Framework webpack.
* docs: kibana developer docs
This is the beginning of developer-focussed docs for Kibana. The content
is mostly pulled directly from the old wiki in the github repo.
* docs: known plugins for 5.x
