kibana/packages/kbn-managed-vscode-config
Luke Elmers b6287708f6
Adds AGPL 3.0 license (#192025)
Updates files outside of x-pack to be triple-licensed under Elastic
License 2.0, AGPL 3.0, or SSPL 1.0.
2024-09-06 19:02:41 -06:00
..
src Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
index.ts Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
jest.config.js Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
kibana.jsonc Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
package.json Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
README.mdx fix <DocLink> usage 2022-08-08 10:26:07 -05:00
tsconfig.json Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00

---
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.