27 June 2017

Keeping up with Kibana: This week in Kibana for June 26, 2017

By Jim Goodwin

Welcome to Keeping up with Kibana! This is a weekly series of posts on new developments in the Kibana project and any related learning resources and events. 


Design

  • [UI Framework] Define consistent default, small, and wide sizing for form fields, and support them within ExpressionItems #12190
  • [KuiKeyboardAccessible] Using parallel language to remove ambiguity #12356
  • [UI Framework] Add new color picker component #12245 #1242226977682-bf8645e8-4cf6-11e7-8d58-3bdf720791db.png

Discovery

  • [Accessibility] Avoid empty th in doc-table header row #12364

Platform

  • The initial new Platform pull request was merged into a feature branch (`new-platform`), where will keep working on it until it’s ready for a PR into master.
  • We moved Jest config into a JSON file instead of being in JavaScript, as that enables a couple features that rely on reading the config file itself (such as running an external node debugger).
  • Update files_to_commit to find renamed files #12423

Sharing

  • Show an error notification, not a full screen fatal error page, when a save fails on dashboard or visualizations #12381
  • Fix reporting bug where saved searches with no results would cause reports to fail #12380
  • Full screen mode for dashboards #1226526991481-72e7c568-4d28-11e7-9367-c95cced1b4ae.gif
  • #12425 #12239 Laying ground work for migrating Field Formatters from client only to being available on both the client and server to support Field Formatters with CSV export.

Visualizations

Bug  fix edition:

  • Look&feel improvemnts for K6
    • Fix appearance of error indicator in Visualize sidebar #12410
    • Fix ui-select error border color and placeholder font color #12411
    • Make vertical bar chart gutter widths consistent #12264
    • Add github-markdown.css to markdown visualization #12377
  • 5.x fixes
    • Scaled date format for date histogram aggregation #12384
    • Ensure scale type, percentage formatting, and font size are preserved on the Dashboard #11958
    • Charts no longer require a minimum size, avoiding “vislib container too small” errors. #11951