mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 10:23:14 -04:00
We're seeing infrequent but reliable build failures due to parse errors when linting - https://buildkite.com/elastic/kibana-on-merge/builds/27649#01869780-fb18-4a4d-990e-b8d5a05a701a/225-792. Looking into bug fixes upstream. |
||
---|---|---|
.. | ||
helpers | ||
rules | ||
index.ts | ||
jest.config.js | ||
kibana.jsonc | ||
package.json | ||
README.mdx | ||
tsconfig.json |
--- id: kibDevDocsOpsEslintPluginTelemetry slug: /kibana-dev-docs/ops/kbn-eslint-plugin-telemetry title: '@kbn/eslint-plugin-telemetry' description: Custom ESLint rules to support telemetry in the Kibana repository tags: ['kibana', 'dev', 'contributor', 'operations', 'eslint', 'telemetry'] --- `@kbn/eslint-plugin-telemetry` is an ESLint plugin providing custom rules for validating JSXCode in the Kibana repo to make sure it can be instrumented for the purposes of telemetry. ## `@kbn/telemetry/instrumentable_elements_should_be_instrumented` This rule warns engineers to add `data-test-subj` to instrumentable components. It currently suggests the most widely used EUI components (`EuiButton`, `EuiFieldText`, etc), but can be expanded with often-used specific components used in the Kibana repo.