* Add main nav tabs with sub tabs for new nav
* move transforms to top level main nav
* Make top nav normal font weight
* Update breadcrumbs to take top nav into account
* proper spacing when settings selected
* fix localization error
* Fix functional tests. Update breadcrumbs
* revert analytics breadcrumb update. save for follow up
* ensure main/sub tabs align left
* update dataVisualizer breadcrumbs
* update typescript for tabs
* General structure of Public w/ legacy brace + autocomplete 🤔
Refactor Resizer functionality (panel component)
Refactor Play Button
Refactor Auto-completion
Refactor Docs opener
Refactor Storage
* First refactor of kbn ace keyboard mode to TS+React
* clean up unused props
* console_menu.js -> console_menu.tsx
* Remove unused file from quarantine and added fixed ui ace keyboard mode react hook
* - Refactored history and storage to app-wide services
- Pre-emptive changes to tests
- sense-history -> HistoryList
- removed unused kbn top nav v2 component
* A lot of cleanup, re-introduced editor resize checker, re-introduced history viewer as TS+React. `history` still needs refactoring.
* First iteration of tap nav menu, with history toggle working
* Lots of fixes
Also moved over and integrated remaining three react components
* Moved a lot of files around again, tidied up NP set up
* Replace angular directive
* Remove used code
* Re-order imports and move all ace dependencies to same location
* Remove more unused code
* Revise quarantined setup mocks
* Don't suggest 'undefined' or other null-like values in autocomplete
* Clean up api_server folder
* Re-add missing style
* Updated karma spec mock
* Fix editors cutting of at bottom of screen
* Refactor console editors into single components
Refactor a lot of business logic to main.tsx container
Minor renaming of variables for better readability
* Updated use of contexts with better error message
Fixed broken render sync cycles (using useCallback)
Fixed Main container render cycle (added missing deps to useEffect)
Fixed default input and removed auto indent from being called on init for already formatted text
* Updated test mocks
* Update to be more in line with NP conventions https://github.com/elastic/kibana/blob/master/src/core/CONVENTIONS.md
* Update console history when making new requests
Fixed spacing between editor and console history
Moved registration of keyboard commands to TS
Fixed setup_mocks.js after renaming app to application
* Clean up git merge conflict artifact
* Use updated NP interfaces
* More typings fixed after updating local project dependencies
* Removing some dependencies on KUI and font awesome from legacy editor
* Fix clear history not re-rendering
Refactor prop name to be more descriptive
* Simplify split_panel and add tests
* Fix accessibility tabbing behaviour for ace editor
* Refactor ConsoleEditor into two separate components
Remove unused changeCursor code
Remove unused textArea ref
Use default lodash debounce (remove unnecessary arg)
* Major a11y fix when tabbing
Major fix for ace in IE11 and Edge browsers
* Update comment
Renamed the misleadingly named AlertInstance.fire to scheduleActions, as it does not in fact "fire" the actions, but rather schedules them to be executed by the Task Manager at the next available opportunity.
## Summary
To indicate they accept droppable data providers, this PR applies highlighting to the Timeline flyout badge and data providers drop area.
Tested in dark and light mode in:
- Chrome `76.0.3809.132`
- Firefox `69.0`
- Safari `12.1.2`
## Timeline data providers (drop area) highlighting behavior
- While a data provider is being dragged, in a page or from within the timeline itself, apply `euiColorSuccess` to the timeline data providers drop area's dashed borders and "plain" text, but NOT to the other primitives, i.e. data provider badges, `AND` / `OR` circular badges, lines, etc
- While a data provider is being dragged, in a page or from within the timeline itself, but NOT hovering over the data providers drop area, apply the `euiColorSuccess` color with `10%` alpha channel to the background of the data providers drop area
- While a data provider is being dragged over the drop target area inside the data providers drop zone, apply the `euiColorSuccess` color with `20%` alpha channel to the background of the data providers drop area
- While a data provider is being dragged over the drop target area inside the data providers drop zone that will add the data provider as an `AND` clause, apply `euiColorSuccess` color to the dashed border, and fill the background with the `euiColorSuccess` color with `30%` alpha channel to the background of the data providers drop area
- Do NOT apply highlighting styles when a column or field (non-data provider) is dragged from the timeline or the `Events` widget
### Dark mode
### Light mode
## Flyout button highlighting behavior
- The (default) timeline flyout button is styled as non-filled EUI button
- The button text reads `Timeline ^` (with a trailing caret), instead of `T I M E L I N E`
- Hovering over the flyout button while NOT dragging underlines the flyout button text, but does not fill the background
- When a user starts dragging a data provider, apply `euiColorSuccess` to all visible flyout button properties (e.g. border, text)
- While a data provider is being dragged, in a page or from within the timeline itself, but NOT hovering over the flyout, apply the `euiColorSuccess` color with `10%` alpha channel to the background of the flyout button
- While a data provider is being dragged, in a page or from within the timeline itself, AND hovering over the flyout such that it's in a droppable state, apply the `euiColorSuccess` color with `20%` alpha channel to the background of the flyout button
- While a data provider is being dragged, in a page or from within the timeline itself, AND hovering over the flyout such that it's in a droppable state, replace the `Timeline ^` with a circle containing a `+` plus sign
- Apply `EuiNotificationBadge` styling to the data providers badge count, and position it in the upper left-hand corner
- Do NOT apply highlighting styles when a column or field (non-data provider) is dragged from the timeline or the `Events` widget
### Dark mode
### Light mode
Resolves https://github.com/elastic/siem-team/issues/457
* Pipeline
* WIP some work for parallelization with ciGroups
* Fix xpack kibana install dir, and add some debugging
* Attempt to quick fix a few tests
* Revert "Revert "Revert "[ci] compress jobs for CI stability" (#44584)""
This reverts commit 078ac2897f.
* Recombine test groups, and try runbld again
* Mostly cleanup, and fix failed_tests reporting to hopefully work for both pipeline and non-pipeline
* Fix typo in shell script
* Remove some debug code
* Add support for changing es transport.port during testing via TEST_ES_TRANSPORT_PORT
* Fix test that uses hard-coded es transport port and add it back in to parallel groups
* Disable checks reporter again for now
* Set env var for TEST_ES_TRANSPORT_PORT in pipeline
* Update Jenkinsfile for shorter testrunner labels
* Fix another hard-coded transport port
* Fix a new test with hard-coded URLs
* Jenkinsfile cleanup and fix one of the groups
* Fix double slash
* Testing vault credentials on jenkins server
* Add a non-existent credential
* Revert "Add a non-existent credential"
This reverts commit 0dc234c465a5483b1a994cb510a182fef766e9cc.
* Try github-checks-reporter again
* github-checks-reporter should only run for elastic/kibana, forks won't work
* Clean up some debug code
* Changing names around to try to make BlueOcean UI a little better
* Add more stages
* Make some changes to stage structure to mirror a nested example from CloudBees
* Handle TODOs, and some cleanup in Jenkinsfile
* Pass GIT_BRANCH when started without GHPRB, fix branch check
* Fix mailer problem and add code that ensures all tests are in cigroups back in
* Test adding worker/job name to junit report paths
* Remove some duplication from ci_setup scripts
* Fix unit test that uses junit path
* Don't reinstall node every time setup_env is run
* Fix yarn install logic
* Fix another unit test that uses junit output dir
* Download latest ES snapshot after kibana builds
* Make sure junit reports are always processed
* Add two failing tests for testing purposes
* Add support to Jenkinsfile for kibana build e-mails
* Remove some debug code for email sending
* Change JOB env handling in junit paths and move it to a sub-directory
* Revert "Add two failing tests for testing purposes"
This reverts commit 5715203e26922a93483feb0ebb8bb3fdcc3daf8c.
* Fix junit report path in test
* Don't send kibana emails on build abort
* Address PR feedback, formatting and use built-in url formatting library
* Fix path formatting for functional test
* Add email sending back in to Jenkinsfile
* Fix another unit test with path problem
* Fix main search bar to top of screen
By allowing overflow on the main content, we implicitly fix the sibling
search bar in position.
elastic/code#1606
* Allow search suggestion text to be truncated
This gives the parent element a width, so that our text-overflow
rules apply to these elements.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1086218#c4 for details
on the issue.
* Fix alignment issue with overflowed search suggestions
If both the icon and the text are allowed to grow/shrink as needed,
flexbox will grow truncated text based on its original width, leading to
subtle sub-pixel alignment issues with other rows.
By fixing the icon to a specific width, we can ensure that the
suggestion text does not grow too big.
* Remove unneeded CSS
We don't need to flex these elements currently as they contain either no
children or inline elements only.
* style: prefer camelCase element names over hyphens
* Fix search result suggestion overflow on IE
Without this directive on the parent, it had no width or flex growth and
didn't respect the parent width. This allows it to take on the correct
flexed width, and thus take on the overflow rules.
* Remove unused CSS rule
We have an overriding align-items declaration immediately after this
one.
* wip to apply kql when refresh on hosts page
* refactor to have less re-render
* add network and timeline page
* fix/add unit testing
* from review remove any effect from render
* clean up + review II
* review II + bug fixes
* review III
* SQL template with triple quote in completion
* Slight update to SQL query template and bugfix for collapse/expand of request bodies
* Add comment and slight update to triple quote expansion
* Updated tests after changes to newline behaviour
* Restore old backslash triple quote expansion behaviour
* Handle some more tricky cases, but make sure to preserve newlines.
Update tests for new cases too
* Make regex more specific
Expanded tests
* Now make it x-browser
* Slight refactor and renaming
* Update comment
This changes the job health check of the log analysis page to consider finished jobs as healthy. This situation is relevant when the job is non-continuous, i.e. created with a definite end date.
At the same time it ensures that datafeeds that failed to be started due to empty indices lead to the jobs being considered unhealthy.
fixes#45180
* SQL template with triple quote in completion
* Slight update to SQL query template and bugfix for collapse/expand of request bodies
* Add comment and slight update to triple quote expansion
* Updated tests after changes to newline behaviour
* Restore old backslash triple quote expansion behaviour
