ae0e51e824
* Fix NES cached suggestion not shown after rebasing over user indentation When a cached NES suggestion is a line-based insertion that restates the line's indentation (e.g. predicting " return [" on an empty body line) and the user tabs to indent that line, tryRebaseCacheEntry served the raw, non-minimized edit whose range spans the indentation the user already typed. That edit is not a clean at-cursor insertion, so the core inline-completions renderer drops it and the cached suggestion is silently not shown. Minimize the served rebased edit via removeCommonSuffixAndPrefix so the indentation the user already typed is stripped, yielding a clean at-cursor insertion that renders as ghost text. This is semantically neutral (same apply() result on the current document) and idempotent for the downstream isRejectedNextEdit check. Minimizing is done at the cache serving layer rather than in editRebase, which intentionally keeps the full line edit for response/telemetry fidelity. Adds a regression test covering the empty-line + tab scenario. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 02c9dab3-1534-4b24-86c1-410c66e9d550 * Salvage NES suggestion on rebaseFailed for indentation mismatch The previous commit minimized the served edit in the rebase *success* branch, but that path already renders as ghost text, so the change was a semantic no-op and its test modeled an artificial success path. The real bug is in the rebase *failure* path: strict rebase matches indentation literally, so when the user re-types a line's leading whitespace differently than the model predicted (e.g. pressing Tab to insert a tab character, or a different number of spaces, on an empty body line), the whole suggestion is silently dropped and nothing is shown. Salvage that case in the cache layer: on `rebaseFailed`, re-anchor the model's still-valid content as a clean at-cursor insertion that respects the indentation the user actually typed. This mirrors the reconciliation the engine already performs when the indentation matches, is a faithful representation of the model's intent (so it upholds the display layer's soundness invariant), and only fires when the suggestion would otherwise be dropped. Revert the no-op minimization and replace the misleading regression test with a faithful one covering the tab-character drop scenario (which fails without this salvage). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 02c9dab3-1534-4b24-86c1-410c66e9d550 * Gate NES indentation-mismatch salvage behind a setting Put the rebaseFailed re-anchoring behavior behind a new team-internal, experiment-based setting `chat.advanced.inlineEdits.reanchorContentOnIndentationMismatch` (default off) so it can be rolled out or disabled independently. Thread the flag through `NesRebaseConfigs` (built in `_getNesRebaseConfigs`) and gate the `tryReanchorContentAfterIndentation` salvage call on it. Add a regression test asserting the suggestion is dropped when the setting is disabled, alongside the existing salvage test with it enabled. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 02c9dab3-1534-4b24-86c1-410c66e9d550 --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Visual Studio Code - Open Source ("Code - OSS")
The Repository
This repository ("Code - OSS") is where we (Microsoft) develop the Visual Studio Code product together with the community. Not only do we work on code and issues here, but we also publish our roadmap, monthly iteration plans, and our endgame plans. This source code is available to everyone under the standard MIT license.
Visual Studio Code
Visual Studio Code is a distribution of the Code - OSS repository with Microsoft-specific customizations released under a traditional Microsoft product license.
Visual Studio Code combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.
Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on Visual Studio Code's website. To get the latest releases every day, install the Insiders build.
Contributing
There are many ways in which you can participate in this project, for example:
- Submit bugs and feature requests, and help us verify as they are checked in
- Review source code changes
- Review the documentation and make pull requests for anything from typos to new content.
If you are interested in fixing issues and contributing directly to the code base, please see the document How to Contribute, which covers the following:
- How to build and run from source
- The development workflow, including debugging and running tests
- Coding guidelines
- Submitting pull requests
- Finding an issue to work on
- Contributing to translations
Feedback
- Ask a question on Stack Overflow
- Request a new feature
- Upvote popular feature requests
- File an issue
- Connect with the extension author community on GitHub Discussions or Slack
- Follow @code and let us know what you think!
See our wiki for a description of each of these channels and information on some other available community-driven channels.
Related Projects
Many of the core components and extensions to VS Code live in their own repositories on GitHub. For example, the node debug adapter and the mono debug adapter repositories are separate from each other. For a complete list, please visit the Related Projects page on our wiki.
Bundled Extensions
VS Code includes a set of built-in extensions located in the extensions folder, including grammars and snippets for many languages. Extensions that provide rich language support (inline suggestions, Go to Definition) for a language have the suffix language-features. For example, the json extension provides coloring for JSON and the json-language-features extension provides rich language support for JSON.
Development Container
This repository includes a Visual Studio Code Dev Containers / GitHub Codespaces development container.
-
For Dev Containers, use the Dev Containers: Clone Repository in Container Volume... command which creates a Docker volume for better disk I/O on macOS and Windows.
- If you already have VS Code and Docker installed, you can also click here to get started. This will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
-
For Codespaces, install the GitHub Codespaces extension in VS Code, and use the Codespaces: Create New Codespace command.
Docker / the Codespace should have at least 4 cores and 6 GB of RAM (8 GB recommended) to run a full build. See the development container README for more information.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
License
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT license.