mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 02:09:32 -04:00
12aeaa8101
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. |
||
|---|---|---|
| .. | ||
| common | ||
| public | ||
| server | ||
| kibana.json | ||
| README.md | ||
| tsconfig.json | ||
Field formats example
Field formats is a service used by index patterns for applying custom formatting to values in a document. Field formats service can also be used separately from index patterns.
This example plugin shows:
- How field formats can be used for formatting values
- How to create a custom field format and make it available in index pattern field editor
- How to create a custom editor for a custom field formatter