mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
a41badf964
## Summary * Remove some old paths pointing to `packages/kbn-pm` (no longer exists). * ~Fix group and visibility for `@kbn/streams-app-wrapper-plugin`~. (done in https://github.com/elastic/kibana/pull/212210) * Update `scripts/relocate` logic with latest enhancements. * Convert `@kbn/observability-synthetics-test-data` folder name to camel-case (messes up with pre-commit hook). |
||
|---|---|---|
| .. | ||
| src | ||
| index.ts | ||
| jest.config.js | ||
| kibana.jsonc | ||
| package.json | ||
| README.mdx | ||
| tsconfig.json | ||
--- id: kibDevDocsOpsManagedVscodeConfig slug: /kibana-dev-docs/ops/managed-vscode-config title: "@kbn/managed-vscode-config" description: Config options for vscode that are automatically setup for contributors date: 2022-05-24 tags: ['kibana', 'dev', 'contributor', 'operations', 'vscode'] --- This package contains VSCode settings which are automatically setup for contributors on bootstrap. This is done via the <DocLink id="kibDevDocsOpsManagedVscodeConfigCli" /> using `node scripts/update_vscode_config`. In order to support contributors maintaining workspace-specific configuration of their own, this tool prefixes all managed config settings with `// @managed` comments. If you want to override any config that is `// @managed` then just update that comment to `// self managed` and the update script won't touch that key/value. `// self managed` comments are only necessary for keys which are currently or might become managed in the future. Config keys which are not managed are always preserved when updating the `.vscode` directory.