kibana/examples/partial_results_example
Spencer 12aeaa8101
[ts/checkProjects] validate extends of all ts projects (#145176)
Fixes https://github.com/elastic/kibana/issues/145129

In order to make our TS setup in the repo far more efficient we needed
to make it a little more complicated than it used to be. This includes a
few rules that all tsconfig files need to follow which were currently
assumed to be true, but with this PR will now be validated:

1. No tsconfig.json files are allowed to extend the `tsconfig.json`
file. This file is used to produce types for the root of the repo, and
include the `package.json` file in a project so it can be referenced in
projects directly. Files which violate this rule were updated to point
to the root `tsconfig.base.json` file.
2. Every tsconfig.json file must extend the `tsconfig.base.json` file,
either directly or indirectly.
2022-11-16 08:57:51 -07:00
..
public [Expressions] Add a flag to opt out of the partial results in the expressions (#144241) 2022-11-04 13:20:46 +01:00
kibana.json [Expressions] Partial results example plugin (#113001) 2021-09-27 18:54:05 +02:00
README.md [Expressions] Partial results example plugin (#113001) 2021-09-27 18:54:05 +02:00
tsconfig.json [ts/checkProjects] validate extends of all ts projects (#145176) 2022-11-16 08:57:51 -07:00

Partial Results Example

The partial results is a feature of the expressions plugin allowing to emit intermediate execution results over time.

This example plugin demonstrates:

  1. An expression function emitting a datatable with intermediate results (getEvents).
  2. An expression function emitting an infinite number of results (countEvent).
  3. A combination of those two functions using the mapColumn function that continuously updates the resulting table.