<p dir="auto">Allow extensions to specify they are deprecated in their <code class="notranslate">package.json</code>, with an optional alternative extension(s) field. This setting can inform the user of the deprecation in-product, and if specified, potentially update to the new extension automatically without informing of the deprecation?</p>
<p dir="auto">Related: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="138153160" data-permission-text="Title is private" data-url="https://github.com/microsoft/vscode/issues/3670" data-hovercard-type="issue" data-hovercard-url="/microsoft/vscode/issues/3670/hovercard" href="https://github.com/microsoft/vscode/issues/3670">#3670</a></p>
<p dir="auto">It's getting more common to use YAML for configuration. For example <code class="notranslate">docker-compose.yml</code> or Swagger files are usually written in YAML. The JSON Schema based autocomplete for JSON files is a neat feature, please enable that for YAML files also.</p>