* Switch to Yarn (#15485)
* switch to yarn
* cleanup misc references to npm
* [yarn] loosen dependency ranges so yarn will merge more deps
* fix linting error now that moment uses ESM
* [licenses] font-awesome changed the format of its license id
* Use local yarn
* Misc fixes
* eslintignore built yarn file
* Remove mkdir which doesn't do what it should do
* Check build without upgrading lots of versions
* Fix license check
* too many moments
* Better description
* Review fixes
* Lock to angular@1.6.5
* More specific version locks
* Revert "More specific version locks"
This reverts commit 11ef81102e.
* Revert "Lock to angular@1.6.5"
This reverts commit 3ade68c14c.
* rm yarn.lock; yarn
* Forcing a specific version of React, Angular, Moment
* Using vendored version of yarn in ci
* Use --frozen-lockfile
* fixes
* Update lockfile
* Reverting a258f1af4
* Revert "[TSVB] Add support for Math Aggregation to tables (#14553)"
This reverts commit d2537d8039.
* Revert "Math Aggregation to support Sibling Aggs for TSVB (#13681)"
This reverts commit 9c9fb17fef.
* removing old partial bucket cliping from table vis
* Adding support for percentiles for bucket_script args
* removing old partial bucket cliping for table vis
* Fixing support for drop last bucket
* Adding unsupported agg message
By setting cache-control to must-revalidate, we indicate to the browser
that it should send the if-none-match header with the last known etag
value. If the etags match, the server responds with a 304 and no body,
and if they don't the server responds with a 200 and a body along with a
new etag.
This ensures a cache is always invalidated when a bundle changes, like
when Kibana is upgraded or a plugin is installed.
We no longer send the last-modified header because we don't want the
browser caching based on time. Doing so can be unpredictable since the
browser may not agree with the server's definitions of DST, and the
server time itself can be changed.
* Fix broken collapse of editor
* Fix broken styling in small editor mode
* Remove unneeded media query
* Revert "Fix broken collapse of editor"
This reverts commit 1e909b3cf1.
* replace KuiConfirmModal with EuiConfirmModal
* add titles to confirm modals. Update modal text and button text
* updates for newest version of EUI
* use EUI class in overlay and EUI button constants
* remove logic about changed filters in cancel dashboard editing modal, clean up wording for import saved objects modal
* fix broken function test - management delete index pattern
* wrap names in single quotes
* Exposing the sharing title on the controller
* Implementing the getSharingType on the controllers
* Adding a getSharingSavedObjectId method
* We don't need the savedObjectId anymore
Previously, we were not aggressive in combining common code which resulted in duplicates included in the bundles.
As an example `node_modules/elasticsearch-browser/elasticsearch.angular.js` is present in the following chunks:
* kibana.bundle.js
* dashboardViewer.bundle.js
* apm.bundle.js
* monitoring.bundle.js
* ml.bundle.js
* timelion.bundle.js
* graph.bundle.js
Vendor code (anything inside Kibana's node_modules) is placed in vendors.bundle.js while everything else with more than two references is placed in commons.bundle.js.
This has a couple positive side-effects (numbers are with x-pack & canvas):
* Decreased build time. Seeing builds go from 475.76 seconds to 274.72.
* Decreased memory overhead. Uses roughly 1/3 the memory overhead.
* Decreased bundle size. A 68% reduction in overall bundle size. Going from 66.16 MB to 21.13 MB.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* [ui/bundles][optimizer] only use caches when in dev mode
* [optimize/caching] make cache-loader disabling more explicit
* [optimize/caching] clarify why we only want caching in dev
* Naively switching to Observables
* Dispatching native renderStart and renderComplete events
* Emitting actual event...
* Removing the visualize debounce
* Fixing unsubscribe
* Dispatching correct event for the metric visualization
* Moving the $scope.$apply to right after the call to render so it does
what it's supposed to
* Switching angularjs attribute name
* Removing the renderStart since it doesn't do anything
* Removing the renderComplete trigger from visualize, since no one listens
at this level
* Using vis.requestError to communicate when there's a request error
* Grabbing the container when creating the observable
* Dispatching renderStart as soon as we can
* Only emitting renderComplete after we wait for a new animation frame
* Can't ignore the first resize, sometimes it's actually a resize
* Use $timeout in visualiationEditor render, it can be in a digest already
* Calling renderComplete in componentDidUpdate as well
* Switching tests to use render-complete
* Fixing peer review corrections from @gammon
* Removing visDiv reference, we don't need it anymore
* Removing requestAnimationFrame
* Removing unused $timeout
* Removing test that was testing an implementation detail
* Adding $timeout.flush
* Moving the failures to the actual tests don't work.
* Deleting tests that weren't running before
* Removing import of removed test
* Consolidating the dispatchRenderComplete/dispatchRenderStart
* Beginning to work on image advanced setting type
* Making the maxSize code and UI more user-friendly (hopefully).
* Getting rid of that border, I was using the wrong class
* Displaying an image for the preview
* Not displaying the image if we don't have a value
* Removing no longer used code
* Adding explicit throw in the subscription to make our intents more clear
* Changing some of the Observable style based on input from the peer review
* Using the maxSizeKB option to enforce the size
* Adding support for no max
* Throwing better errors
* No longer duplicated the multiple usage error message
* Using the maxSize attribute to control the max size of the settings
* No longer using JSON.stringify, it's already a string and that approach
won't really do anything for other data-types
* Extracting validate to it's own method
* No longer hardcoding the maxLength validation in the uiSettings
* Using a Joi schema instead
* Punting on server-side validation for the time being
* Upgrade to jQuery 3.2.1
The jquery-migrate showed a number of warnings,
but no errors, so it should be safe to use.
Warnings mostly related to bind, unbind, focus, ...
https://github.com/jquery/jquery-migrate/blob/master/warnings.md
To enable jquery-migrate, I added it to package.json, and added
a require('jquery-migrate') to the webpackShims/jquery.js right
after the require('jquery').
* Breaks in jQuery3: $(window).offset()
* await field.type(), update chromedriver
* Fix design of debug spy panel
* Simplify the debug spy panel
* Fix height of spy content
* Use scope bindings for spy
* Allow modes to be enabled/disabled based on vis
* Make showSpyPanel docs for loader more detailed
* Only show default panels when using courier
* Fix styling of req/resp spies
* Fix title styling in spy panel
* Get rid of visData in spy panels
* Use tabs instead of select box
* Ensure uiState in spy
* Restyle code in default editor
* Remove unnecessary if protection
* Use local scope variable for rowsPerPage
Due to issues with primitive datatype bindings in Angular this anyway
didn't save it correctly back into the variable.
* Pull all logic into spy directive
* Fix bug when closing panel
* Check for minimum chart size
* Skip spy tests for now
* Fix functional tests
* Improve uiState mock
* Create unit tests
* Remove dead scope binding
This makes use of the `auto_expand_replicas` setting to keep `.kibana` green on one node clusters, which should help to create a better starting experience.
