This upgrades TypeScript to version 2.9.2. My main motivation is the support for generic type arguments in JSX elements and tagged templates (e.g. for `styled-components`).
Problems arising from breaking changes in the new TypeScript version have been mitigated by:
* setting the `keyofStringsOnly` option until impacted code has been
future-proofed
* Restricting some joi-related generics
See the [release notes](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-9.html) for details.
Some follow-up tasks should be:
* Update EUI to support the new `keyof` behaviour
* Update new platform TypeScript code to support new `keyof` behaviour
* Remove `keyofStringsOnly` setting
fixes#20741
Rather than just generate random words with the default length of 2, generate a random 5 letter word for the type to filter by and 10 letter words for the other types, so there will never be more than 3 records with `type1`.
* fix metrics field name (stats)
* add state info
* add module name count
* use a set for the unique hosts instead of a map
* fix getting beats_state info
* fix unit test
* processBeatsStatsResults and processBeatsStateResults
* split to packages in accordance to specific library
* split to packages depending on tech and environment
* make env modules names consistent
* remove intl polyfilling
* move laoder to root, i18n folder to core
* Capitalize the license type in monitoring
* Revert "Capitalize the license type in monitoring"
This reverts commit 38ad3a516d.
* Pass in the type capitalized
* Revert "Pass in the type capitalized"
This reverts commit 6a05bb12f3.
* Capitalize type in license status directly so consumers do not need to worry about it
* Adding fontSize from variables
* SectionHeader style added
* Adding section headers
Needed titling for DB statement and Stacktrace on the page
* Pluralization
* Adding fontSize variable
* Creating new header title style
* Moving title into Stacktrace container
* Updated snapshots
`node scripts/tslint` is used to run the linter on all projects, but isn't currently reporting a non-zero status code when there are failures. This PR ensures that the status code is always 1 when an error occurs in the linters.
To test make a change to a TypeScript file that violates the linter rules and run `yarn grunt run:tslint` to make sure that `grunt` is seeing the non-zero exit code and fatal-ing correctly.
```sh
yarn grunt run:tslint
echo $? # should be 1
```
* move unsetLogic into react component
* remove extra comment
* add comment about why empty state is needed for InputRange component
* fix broken jest test
* move empty state logic from react component to ListControl class, add comments about reset and clear functions
* add comments about clear and reset to control class
* calculate hasChanged to avoid bug where clear form still shows 'cancel changes' as active for an empty form
* use hasValue in range control to check if value exists
* add unit test for list_control_factory and cleanup range_control from review comments
* unskip reporting tests
* Focus only on flaky test suite and run 10x
* Revert "Focus only on flaky test suite and run 10x"
This reverts commit a6616b1140c29d8d3f13666d20ae94db9a97267f.
* refactor login page check, turn off telemetry
* significant refactor of navigateTo
* replace slashes with _ in test failure output html files
* re-do out of date PR
The pseudo-element agg-type-select-wrapper::after which represents the dropdown's arrow didn't react to the click element of the dropdown itself. pointer-events: none is now added to the pseudo-elements to let the click pass through to the element intented to react on the click.
* Test dependency upon msearch. Add NoDigestPromises to test suite to simplify tests.
* Test the returned promise resolution value.
* Add tests about aborting situations.
* Add test for when the request is aborted while it's in flight.
* Test implementation details regarding interaction with searchRequests.
* Change callClient to return ABORTED for requests which have been aborted.
* Add test verifying that esPromise.abort() is called.
* create saved object client that is native javascript
* fix savedObjectClient unit tests
* get saved object client from chrome when being used outside of angular
* update error handlers to pull status code from FetchError
* add some debug messages to failing functional test
* revert changes to management/_objects
* add clicks to import done in import objects test
* take screenshots of test only failing in CI
* remove functional test screenshot code since test is passing in CI now
* remove unused file, clean up saved_objects_client test to not use global, add test to error_auto_create_index to ensure compatibility with kfetch errors
* add body to kfetch error
* update savedObjectClient.bulkCreate
* add bulkCreate wrapper to SavedObjectsClientProvider
* mark _createSavedObject and _processBatchQueue as private methods
