* [indexPatterns/field] replace mapping awareness with readFromDocValues
* move link to more details to proper location
* Address kjbekkelund's feedback
* let the prs speak for themselves
* Implement a way to hide write controls from dashboard
* Add roles definition to the saved dashboard object
* Remove roles from dashboard
* Use an angular provider to control the hideWriteControls flag
* Add an api to chrome to show only a single app by id
* Refactor injectVars logic
* Fix tests
* Refactor kibana root controller
* add additional test functionality
* Missed a couple spots for hiding edit controls
* add retry and help text for dash only mode failures
See if it helps. Tests pass locally.
* Move element into screen when clicking
* use shorthand for object creation
* Hide checkboxes, show 'no dashboard' message with the button
* [utils] add util for converting between es and kibana types
* [utils/kbnFieldTypes] use random strings instead of numbers
* [utils/kbnFieldTypes] ensure that castEsToKbnFieldType() returns correct instance
* [utils/kbnFieldTypes] change getEsTypes() -> getKbnTypeNames()
* [fieldEditor] update test to validate limited type support
* [fieldEditor] unexpected scripted field langs should list all kbn types
* [test/stubbedLogstashIndexPattern] fix kbnFieldType use
* [utils/kbnFieldTypes] remove unused castEsToKbnFieldType() fn
* [utils/kbnFieldTypes] don't use Object.freeze()
Object.freeze() keeps properties of an object from being redefined or removed, which we want for the kbnFieldTypes, but it also prevents them from being iterated by angular since angular needs to add a unique `$hashKey` property to each object. To keep the properties read only but allow extension KbnFieldType uses Object.defineProperties() instead.
* [fixtures/logstashFields] fix use of "unknown" and "conflict" types
* [stubs/logstashFields] mention why "conflict" is special
* [utils/kbnFieldTypes] check complete output of getKbnTypeNames()
* [indexPatterns/create] make loading state independent of fieldsFetchError
* [indexPatterns/create] return promises while loading
* [indexPatterns/create] track loading count in controller
* [grunt/build] refactor _build:notice task to not depend on npm
The _build:notice task used to rely on the output of `npm ls` to determine where modules were defined, but the task now just asks `license-checker` to include the `realPath` of the modules it describes in it's output, which is ultimately the same thing but works with `yarn` too.
* [grunt/licenses] convert to use lib/packages/getInstalledPackages()
* [grunt/notice/generate] test generateNoticeText()
* [grunt/licenses] tested assertLicensesValid()
* [npm] remove npm dev dep
* [tasks/lib/packages] do not include kibana in "installed packages"
* [tasks/lib/notice] join all notices with the same separator
POST /api/saved_objects/{type}
GET /api/saved_objects/{type}/{id}
PUT /api/saved_objects/{type}/{id}
DELETE /api/saved_objects/{type}/{id}
GET /api/saved_objects/{type?}
* Consolide chrome visibility toggle code into single module
* Extracting code into helper functions for better readability
* Removing redundant setting
* Extracting functions to higher level in scope so they are not defined multiple times
* Fixing typo in comment
* Starting to add unit tests
* Actually adding the tests this time
* Adding unit tests for handleGettingStartedOptedOutScenario function
* Binding this to window to prevent Uncaught TypeError: Illegal invocation
* Adding unit tests for handleExistingIndexPatternsScenario function
* Add helper function to aid unit testing
* Refactor unit tests
* Inlining function to prevent naming awkwardness
* Binding this to window to remove ambiguity
* Adding missing import
* Fixing import
* Catching expected error
* Move accessibleClickKeys service into UI Framework.
* Add KuiKeyboardAccessible component to UI Framework.
* Change KuiKeyboardAccessible and kbn-accessible-click to propagate events. This mirrors mouse click behavior.
* Adding some more functionality to the Getting Started page object
* Using optOut method from Getting Started page object
* Adding functional tests for Getting Started page
This set of tests specifically tests the scenarios under which a user should or should not get redirected to the Getting Started page
* Adding log.debug message
* Conforming to HTML style guide
* Using new GettingStarted page object methods + opting out
* Adding test for nav being shown
* Removing unnecessary line
* Navigate to Discover expecting to be redirected to the Getting Started page
* Trying beforeEach instead of before
* Remove LS data index + load empty kibana index
* Removing unnecessary line
* Fixing order of operations
* Removing the auto-apply feature
* Removing commented out code
* Adding auto apply toggle; making apply bar perminant; only make apply sensitive to data changes
* Tweaking the auto apply behavior
* Moved auto apply toggle; added local storage for setting
* Add aria-label and kbn-accessible-click to Local Nav menu buttons.
* Make Share menu keyboard accessible.
* Make datepicker and timepicker keyboard accessible.
* Revert some kbn-accessible-click instances in favor of native button elements.
* Introduce Clone feature in view mode
* Use a new react modal for cloning dashboards
* Fix focus issues and tests
Unfortunately can’t run jest tests outside of the ui_framework at this
time.
* Add tests for dashboard clone modal
* move the jest tests out of the __tests__ directory
It’ll cause failures for the normal unit test runs
* use react instead of angular for overlay and loading of dom element
* Append 'Copy' to the title in the clone dialog so by default it doesn't clash
* address code comments
* [tests/functional] automatically opt-out of getting started page on navigation
* [test/functional/commonPage] avoid circular reference
* [test/functional/commonPage] move check for getting started after url has settled
* [gettingStarted] prevent route resolution by returning halt promises
* [test/functional/commonPage] wait for kibana to load before checking for getting started
* [uiRoutes/setupWork] provide a token that can be thrown to halt setup work
* [ui/routes] rename reference to WAIT_FOR_URL_CHANGE_TOKEN
* address review feedback
* [fieldFormat] make formatted output non-bindable
* [aggTable] totals are consumed as text, produce text
* [tests] fix existing tests
* [fieldFormat/contentType] add tests for non-bindable wrapper
* add help_icon component
* rename to info_button
* build
* info button example
* info button test
* fix example
* change bg color and add padding:0
* make component include all props
* set color with a variable
* use bgcolor transparent
* example guide text fix
* update markup to allow component class to set font-size
* use globalLinkColor instead of new color value
* No longer throw an error to the rest of the stack if there is an error refreshing fields for an index pattern
* Only prevent rethrowing for the certain error scenario
This adds the ability to display a filter bar in the Context view and to apply those filters to the queries. It also modifies the link from the Discover view to the Context view to copy the currently defined filters when switching. New filters can be added from within the Context view using the icons in the expanded detail rows.
This adds several `LocalNav`-related React components and converts their usage in the docs to React:
* `KuiLocalNav`
* `KuiLocalNavRow`
* `KuiLocalNavRowSection`
* `KuiLocalNavTab`
* `KuiLocalNavTabs`
* `KuiLocalNavTitle`
* fix focused button not being set
Need to do it in a timeout because ng-react hasn’t loaded the react
code yet, so it can’t find the buttons.
* add a test
that would have caught the issue, and also change the default focused
button for the listing delete page since it’s a destructive action.
* Add a comment
* Push focusing of default button into react code
* Push ESC key handling into react as well
* Remove ESC tests in angular form
They don’t pass, I’m guessing because of the way it’s triggered, but
these test cases should now be handled in jest. Also confirmed it
works as expected with the modal.
* Address code review comments
* Use autoFocus
The discover:aggs:terms:size config value was never added to the default values, so when the trash-button is clicked it removes the config completely and causes discover to send an empty size param to visualize.
