* skip and adjust functional tests for Firefox
* downgrade geckodriver to 0.22.0
* [ftr] add firefox specific config file
* remove hard coded firefox adjustments
* remove firefox specific screenshot directory
* run functional tests in firefox in x-pack
* pass the logger to readConfigFile()
* rename local var
* skip xpack firefox config
* run xpack firefox functional tests in separate command
* update report name for XPack firefox results
* adjust viz shared item test
* skip shared item test
* [test/feature_controls] increase timeout to 20 sec & use forceLogout
* FF timeout on TSVB, refresh page on failure for url navigation
* [feature_controls/visualize_security] increase timeout to 20 sec
* skip dev_tools_spaces tests on FF
* run all groups 3 times
* skip more func tests
* skip more tests
* skip all feature controls tests for Firefox
* revert back changes in feature controls tests
* rename xpack report for chrome
* skip tile map for FF, wait for render before saving
* Revert "run all groups 3 times"
This reverts commit 12b4f69627.
* revert refresh on login
* apply feedback
* Add date_nanos to date type in kibana field types
* date_nanos by default is formatted by "Date Nanos" format
* Format computed date_nanos field to strict_date_time to prevent rounding
* Hide Discover - "View surrounding documents" btn for date_nanos (will be subject of another PR)
* Append number of nano seconds to formatted timeField
* Add new key dateNanosFormat to UI setting defaults
Solution for use cases that need a query bar without a submit button or date picker that still want KQL and autocomplete. Necessary for the KQL in TSVB and KQL in filters aggregation efforts.
* fix: 🐛 make script input field full width
* test: 💍 update Jest snapshots
* feat: 🎸 add Groovy syntax highlighting
* test: 💍 update test snapshot
* test: 💍 fix scripted field form functional test
* test: 💍 fix more functional tests for scripted field input
* refactor: 💡 use import instead of require()
* EUIficate time interval control
* Update tests
* Remove empty option, update fix tests
* Bind vis to scope for react component only
* Combine two interval inputs into one EuiCombobox
* Add error message
* Add migration script; remove unused translations
* Update fuctional tests
* Update unit test
* Update tests; refactoring
* Use flow to invoke several functions
* Update test
* Refactoring
* Reset options when timeBase
* Add type for editorConfig prop
* Add placeholder
* Fix lint errors
* Call write after interval changing
* Fix code review comments
* Make replace for model name global
* Revert error catch
* Remove old dependency
* Add unit test for migration test
* Fix message
* Fix code review comments
* Update functional test
* EUIficate number interval
* Add type for EditorConfig
* Update functional tests
* Add placeholder
* Update placeholder
* Use FormattedMessage instead of i18n
* Set validity in the effect only
* Refactoring: add showValidation prop and remove isInvalid
* Update prop
The interval parameter is used to fill the gaps between missing buckets. If we are using a calendar interval it not always correspond correctly to his milliseconds representation. E.g. 1y interval can correspond to 365 or 366 days depending on the interval and. If transformed to milliseconds it can get one of those two values depending of the interval start and end. The same happens for months.
Add a new esarchive with 7 years of data, used for those functional tests
Removed angular dependency from zero injection
* Remove skip for testing on server. Unable to repro locally
* run kibana-ciGroup2 40 times per build
* Temporarily skip 'geo map' check
* Left out 'Rendering Test: ' in filter string
* Revert "run kibana-ciGroup2 40 times per build"
This reverts commit 103a5c9c6e.
* Review feedback. Remove 'Flaky' test ref
Attempts to make KQL syntax errors more sensical to the average user.
I initially tried to use a similar solution to the one we used for detecting usage of old lucene syntax. In other words, I tried to create rules in the grammar that would match strings containing common mistakes the user might make and throw custom error messages for each situation. This proved to be more difficult for detecting errors in the regular language. While the Lucene rules could be completely separated from the main grammar, the KQL error rules had to be mixed into the main grammar which made it much more complex and had a lot of unintended side effects.
So instead I decided to lean more heavily on PEG's built in error reporting. Giving certain rules human readable names allows the parser to use those names in the error reporting instead of auto generating a long list of possible characters that might be expected based on the matching rules. Since the PEG errors contain location information I was also able to add ascii art that points the user to exactly where the error occurred in their query string. While this approach is not quite as nice as bespoke error messages that tell the user exactly what is wrong in plain English, it's much more maintainable and I think it still results in much better error messages compared to what we have today.
I've also removed the old original kuery grammar (for queries like is(response, 200)). We were only using it to display an error if I user was still using the old syntax. This version of kuery hasn't existed since 6.3 and we've had error messages telling users this since then. I think it's safe to remove the legacy parser at this point, which greatly reduces the complexity of our error reporting.
* wait for rendering
* run ciGroup12 x60 times
* [visualize/_tsvb_chart] redesign tests
* wait for viz initial loading before navigation
* [visualize/_tsvb_chart] assert tab is loaded
* Revert "wait for viz initial loading before navigation"
This reverts commit 1023db4fb9.
* [TSVB] [Performance]request for api/metrics/fields triggered after all UI changes
Fix: #34433
* [TSVB] [Performance]request for api/metrics/fields triggered after all UI changes - prevent reRender in case of no changes
Fix: #34433
* improve tests
* Revert "[TSVB] [Performance]request for api/metrics/fields triggered after all UI changes - prevent reRender in case of no changes"
This reverts commit a04ed55103.
* Revert "[TSVB] [Performance]request for api/metrics/fields triggered after all UI changes"
This reverts commit 040f0b106b.
* Revert "run ciGroup12 x60 times"
This reverts commit c38427f67f.
* rename dataTestSubj
* Initial work converting UI to use new server side APIs
* Remove missed file
* Fix jest tests
* Code cleanup pt1
* Fix file casing
* Fix jest tests
* Modify UI to support including nested references
* Fix button layout
* Connect includeReferencesDeep, remove references_missing_references logic
* Fix broken tests
* Cleanup
* Display success notifications and auto close modals on export
* More code cleanup
* Log to server when user imports using legacy .json file
* Final cleanup
* Update test snapshots to match updated text
* Apply PR feedback pt1
* Remove isLoading and wasImportSuccessful state variables, use single status variable instead
* Move business logic out of flyout component
* Apply PR feedback
* Update wordings
Now you can use the Enter key to submit the form used e.g. when saving a new dashboard
Good for a11y + a time saver
Adds Form element, migration of Button onClick to Form's onSubmit
Adds functional test for Enter key submission
Fix#30831
* [@kbn/expect] "fork" expect.js into repo
* [eslint] autofix references to expect.js
* [tslint] autofix all expect.js imports
* now that expect.js is in strict mode, avoid reassigning fn.length
