mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 10:40:07 -04:00
e21bec3f31
## Summary After #217202 and #217034 this the another attempt with `lodash` and `lodash/fp`. In short: `lodash` and `lodash/fp` have a special webpack treatment as they are imported within the shared bundle. Now webpack is not smart enough to understand that `import camelCase from 'lodash/camelCase';` is still pointing to `lodash` and it thinks that `lodash/camelCase` is a different package, de-optimizing the bundling caching system. So I’ve tweaked the import to make it point to the shared bundle and save few kbs here and there |
||
|---|---|---|
| .. | ||
| 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.