Changelog:
- [6.15.0](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V6.md#6.15.0)
`index result popularity change popularity should be reset on cancel` has been skipped. This particular test exhibited weird behavior in Chrome when controlled by Selenium. When the button to confirm deleting the index pattern was clicked, it would result in multiple (3-5) calls to the delete saved object endpoint, though only one of those calls was represented in the network tab.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* Fix search issue on listing page + tests
* fix test case inconsistency
* use backtics to create the search string
(cherry picked from commit 31b33659ca)
* [elasticsearch] patch mappings that are missing types
* [elasticsearch/healthCheck] fix tests
* fix doc typo
* [tests/functional/dashboard] fix suite name
* [es/healthCheck/ensureTypesExist] limit randomness a bit
* [test/functional] update es archives with complete mappings
* Index pattern is created, by default, with a random ID by Elasticsearch
* Updated all references requiring the pattern itself to use indexPattern.title
* Advanced options toggle added to index pattern creation page to provide a specified ID
* If an index pattern does not exist, the user is given a link to create a pattern with the referenced ID.
* Preserve the saved vis url when using the add new vis link from dashboard
Fixes https://github.com/elastic/kibana/issues/11078
* Store the edit url in browser history as well
* Fix tests by reordering them.
* add a more explanatory comment
* Revert "When on an embedded page, bypass Getting Started gate check (#12040)"
This reverts commit 05293f1c8d.
* Revert "Making tweaks. (#12003)"
This reverts commit aa3fa06f61.
* Revert "Functional tests for the Getting Started page (#11850)"
This reverts commit 099178a7ca.
* Revert "Prevent flicker on Getting Started page (#11826)"
This reverts commit c4b3ade27d.
* Revert "Getting Started page (#11805)"
This reverts commit 32eff371f2.
* Remove check for Getting Started page from navigateToApp
- Users can now create choropleth maps. This requires configuring an inner join between the results of a term-aggregation and a reference vector layer. This vector layer needs to be in the GeoJson format. By default, Kibana uses vector layers serverd by a data service hosted by Elastic. Users can also bring in their own layers by adding configuration entries in the kibana.yml. These need to point to a CORS-enabled data service that accepts requests from the Kibana application.
- For clarity, the tilemap is renamed to Coordinate Map.
- A new manifest is published by Elastic. this includes metadata for the available tilemap services, as well as metadata for the available vector data layers.
Required manual edits to resolve
Conflicts:
src/core_plugins/kibana/inject_vars.js
* gauge chart
* adding ranges and color options
* adding green to red color pallete
* adding more options
* fixing based on tanya's review
* fixing label positions
* improving range settings
* percentage mode applies to legend
* hidding labels when too long
* updating based on ui rview
* rebasing on master
* adding unit tests
* adding selenium tests
* fixing tests
* adding metric gauge type
* removing metric vis
* adding metric and goal charts
* updating options
* fixing bugs
* fixing based on review from Thomas
* updating icons
* fixing tests
* updating based on last review
* hide some settings if only one range
* fixing tests
* removing unsupported aggs
* fixing defaults
* fixing options
* fixing error with inverse color schema
* adding spacing to info icon
* fixing some tiny issues
* [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
(cherry picked from commit 84ea502205)
* 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
* 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
(cherry picked from commit c9c8e8d066)
Backports PR #11466
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.
* 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
* Getting Started page (#11673)
* Initial code
* Renaming files/folders
* Notes and changes from HTML/CSS review
* CSS changes
* Fixing transform units
* Fleshing out logo circle
* Adding logos
* Un-nesting styles
* Adding kuiText class on <p> elements
* Making shield icon 404 go away
* Using trustAsHtml filter; using registry
* Adding code for registry
* Adding images
* Hooking up the opt-out link
* Fixing linter issues
* Fix issue with refresh bringing back nav
* Removing load_default module
* Use GETTING_STARTED_ROUTE constant
* Allow topMessage to be a directive
* Adding kuiLink CSS class to anchor elements
* Adding alt text to images
* Replace getters with regular methods
* Remove leftover comment
* Removing unnecessary comment
* Fixing typo in comment
* Adding comments for message properties
* Fixing typo in method name
* Defining custom CSS class
* Fixing method call
* Creating custom CSS classes
* Adding documentation links
* Use a instead of button for demo link
* Allow directives in manage and monitor messages
* Refactoring shared code into single ui/public/getting_started folder
* Adding README
* Fixing whitespace in/around links
* Trim messages before setting them
* Decorate in-app links with opt-out attribute
* Opt out of the Getting Started page if the user already has index patterns
* Adding more commentary around expectations of setTopMessage use
* Using ng-src and ng-href attributes where attr values are angular expressions
* Importing the directive before using it
* Using ui/registry for message registries
* Renaming service => helpers to clarify intent
* Adding explanatory comment
* Adding "or"
* Fixing div id
* Breaks out the inject logic into another directive
* Adding Getting Started page object for functional tests
* Consolidate into one registry
* Fixes incorrect classes
* Changes how styles are applied to injected-items items
* Modifying class name per CSS style guide
* Adding getting started doc link
* Removing unused import
* Attempting to fix breaking build
Apparently the Getting Started page is preventing access to Console (Dev Tools, really) so the functional tests for Console are failing. This commit opts the user out of the Getting Started page before attempting to navigate to Console.
* Cleanup on aisle testbed! (#11765)
* Navigate to getting started page so we can opt out of it
* [tests/functional] move screenshots to their own service
* [ftr] add testFailure and testHookFailure lifecycle hooks
* [tests/functional/screenshots] cleanup old screenshots at startup
* [test/functional/screenshots] take screenshots when tests fail
* [cli_plugin/install] fix test
* [ui/scanner] fix test
(cherry picked from commit 2e7fed87fd)
When a user configures a WMS, we should not use the zoom-settings from the manifest. These depend on the user's license level, and are not relevant when using a 3rd party WMS service.
* [indexPattern/create] fix test subject
* [indexPattern/create] only auto-select when there is more than one time field
* [indexPatterns/create] describe weird timeField auto-selection
* [indexPattern/create] update no-date-field text
* restore functional test changes in 02787e3df5
(cherry picked from commit 9f0caba9b6)
* Hide the second toast when adding a new visualization straight from dashboard
* fix tests that assume two notifications
* fix another tests that assumes two toasts
* Change expected data to match change in table UI
* fix more expected results for data UI change
* Revert one previous change and fix one other test
* fix last issues
* missed splitting the last array element
* missed splitting the last array element
* Removing "Index contains time-based events" checkbox
* Rename label
* Adding "No Time Filter field" to time field select list
* Using translation for i18n and consistency with label on create form
* More useful verbiage
* Updating copy
* Adding help block below select for added clarity
* Removing functional tests that used time-based events checkbox
* s/INDEX/INDICES/ to be reflect reality
* Fixing logic error
* Updating functional test to match new behavior
* Use controller property instead of inline expression
* More readable variable name
* add the functional tilemap test (#10992)
Since the unit-tests now verify all colors and sizing as well, this integration test is mainly relevant for verifying the zooming behavior.
* fix test with new template
