This PR removes the ability to create scripted fields with the expression language. It also adds an error message to the scripted field list page if any expression scripts already exist which instructs the user to convert all their scripts to painless.
* Move this logic to a separate directive. Also fix a couple bugs with it around how it interacts with angular.
* Updated variable name
* Handle some edge cases and simplify code
* Fixing typo and further simplyfing code
Introduces bin/kibana-keystore providing create, list, add, and remove actions.
Settings stored within the keystore will be loaded at runtime.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* introduce a mechanism to load a dashboard by title is a single one is found, if not, to refill the search box on the listing page
* Make case insensitive and prevent listing page from "blipping" up on the screen before the redirect
* Add tests
* Add isReadOnly prop to KuiCodeEditor.
* Place cursor at beginning of code editor if it's read-only.
* Surface prompt for isReadOnly mode. Only show cursor when the editor is focused.
* [server/logging] make use of UTC configurable
* [server/logging/tests] try removing TZ from moment
* [server/log/formatJson] use strict equality checks
* [server/log/format] note in method name that time is extracted
* update run REST API to fetch index pattern and use script for scripted fields
* allow scripted fields for elasticsearch split argument
* add test cases for scripted fields to elasticsearch test
* update help text for .es() index argument
* move scripted field check into common file, remove stop characters from index pattern title
* use space instead of nothing for replacing stop chars
* wrap index name in quotes instead of removing dash character
* add a test that will fail due to the current TSVB bug
* add a test to catch the latest bug with saved searches
* reorder array so tests pass
* Update tests since the first panel is TSVB and won't have a spy pane toggle
* get rid of funneling map entry updates through
This was one of the suggestions in the redux discussion but after
sitting with it, I decided I don’t like it. I think it is too much
overhead and makes the code more difficult to read. There are not so
many actions at both levels (touching the whole mapping vs touching a
single mapping object) that justifies this, IMO.
* small refactor of merging panel data logic.
* Fix react proptype warning
React expects panelIndex to always be a string type.
* Add tests to catch panelIndex as a number issue, clean some stuff up.
* Don't update panels in state one at a time when layout changes
* Add test that would have caught the bug
* fix test
Hmmm, I thought grabbing the panels the second time would change their
order predictably but seems no. Still unsure if the order is
garaunteed.
* Need to split out merging panel updates action and setting panels
Tests caught this issue, woot.
* Fix remaining setState warnings by not calling getEmbeddableHander in render
* Fix issue where event isn't set
This method is called from onSubmit without pasing an event which
crashes Kibana.
* Fix broken open buckets
If you leave one side open of an interval, the from/to in the bucket
range will be undefined but null in the config, why this check failed.
* Pass submit event
* arguments suggestions for timelion
* argument_value suggestions
* add incompleteArgument parse failure
* sort suggestions list in domain so index matches selected
* clean up argument replace error, and rename some variables to reflect that suggestions can things other than functions
* add tests for suggestions
* add types text to argument suggestions view
* cjcenizal review updates
* updates from timroes review
* fix raw loader for webpack 3
* make cursor be pointer in timelion expresson textarea
* Show the x-axis value when hovering over a Timelion graph
* Update legend tests
* provide class name for caption styles, reuse single caption element instead of removing/adding
* provide class name for caption styles dark theme
* Add an option to add margins between panels
Make it a boolean useMargins to make this even simpler
* Fix issue with undefined not matching false and triggering a dirty state
* add some test helpers and css for plugin use-age
* default to margins on for new dashboards.
* use const variable syntax for margins
* Fix issue with older dashboards being bumped into useMargins: true mode
* Add tests to catch error
* Fix test
* Don't store column and sort state in panel uiState unless explicitly overridden in a dashboard.
* add debug messages
* Elements can go stale between the find by and the click event so wrap in a retry
* fix bad merge with master
