* add github-markdown.css to markdown visualization
* bring css internal and use kibana variables
* add license from github-markdown-css
* support dark-theme
* full screen mode implementation
* Have Edit and Add buttons kick you out of full screen mode
* Instruct the grid to resize when switching between full screen and regular modes
* Use new styles and listen for ESC key
* handle dark theme
* Remove full screen option from edit mode
It’s awkward with no obvious save button to escape edit mode.
* Code review comments
* deregister the route handler if the user navigates away from the dashboard page.
* Use a new broadcast event rather than hijacking the window resize one
* create registry for field format editors
* index fieldFormatEditors registry by formatId and remove duplicate code between stringify and field_format_editor
* correctly cancel in date format editor and other minor changes
* unnest editor object
* update fieldFormatEditor usage comment to reflect changes
* use ui_exports to load editor registry instead of modules.js
This fixes issues where properties from the visualizations saved in older versions were not applied to the Visualization.
This also addressed the fontSize of metrics not being applied on the Dashboard.
* vary bar widths and keep gutter widths static
* update addGroupedBars to use datumWidth and remove groupCount from addStackedBars
* make datumWidth single function
* remove artifacts of rebase
* Add label and clear link to color picker
* address code comments
* Add extra example for no color label
* Remove unnecessary div
* Add tests for showColorLabel and transparent color choice
* Fix ui-select error border color and placeholder font color.
* Target placeholder selector specifically to the Visualize sidebar to avoid affecting the Filtering UI.
* fixing container too small message
* moving minBarWidth definition to the top
* removing container too small message from point series
* remove tests
* provide getFormat function to date_histogram
* move format object creation to time_buckets
* fix broken test
* pass getConfig to field format constructor since field formatters no longer manage config themselves
* fix _agg_config testing of agg without getFormat method. Old test used date_histogram which now has getFormat, so needed a new agg type
* update expect values for area chart data
* fix expect for visualize app vertical bar
* fix expect for visualize app heatmap chart
* Add new react color picker to ui framework with tests
In prep for dashboard color customization.
* address code review comments
* second round of feedback
* nativeEvent not available in a headless browser, so jenkins tests will fail without a check
* move aria-label
* Require color and have components pass undefined to use default color
* update snapshots after aria-label move
* get rid of default color
* user display: inline-block so clickable is only the width of box and lab el
* remove Private module loader from FieldFormat
* remove dependency on bound_to_config_obj
* update field_formats registry getDefaultInstanc and getInstance to pass getConfig to FieldFormat constructors
* make previous changes work
* remove paramDefaults state from FieldFormat class, instead use getter
* remove use of shortDotsFilter in source field formatter
* fix broken tests
* remove angular dependency from field formatters
* fix _conformance test
* getConfig service and replace with inline function
* remove unneeded ngMock from __tests__/_field_format.js
* use JSON.stringify in content_types instead of aggressive_parse.tojson because function is only converting an array of strings to into a string
* pass getParamDefaults to _numeral in opts argument
* update field format editors to handle moving paramDefaults from class to instance via getter
* remove unneeded reference to self
* change to arrow functions
* change content_type export from object to only the setup function
* remove unneeded function block around simple arrow function
* Provide a way to fetch indices and template index patterns
* Simplify the data structure
* Change the api to expect a query for both fetches
* Add unit tests
* Clarifying comment
* More tests
* - Move logic into ui/public/indices
- Add test to handle duplication logic
* Feedback from PR
* Add toggle (which defaults to on) to suppress 404s
* Leverage existing error handling constructs
- It doesn't push the table down in Discover.
- It squeezes the visualization until it disappears in Visualize and Dashboard.
- Hides the visualize 'no data' error behind the panel by giving it a background color.
The context view error handling assumed that the `Promise` returned by
`SearchSource.fetch()` would be rejected when an error occurred. Due to
the way courier handles errors, this is not the case though. Instead a
globally registered error handler is called (which is leaked beyond the
lifetime of the `SearchSource` when no error occurs) and the promise
stays pending indefinitely.
Because several other parts of Kibana rely on that behavior at the
moment, this adds a new method `SearchSource.fetchAsRejectablePromise()`
which behaves more sanely. It returns a promise that is either resolved
with a successful response or rejected with an error.
