| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
LGTM but a core member may want to look. |
Sorry, something went wrong.
|
Noticed one thing now that this code is actually running. If you have a bunch of comments in a run-up to the old jediEnabled setting, they get removed on edit. E.g., have: // Some
// Comments
// To keep
"python.jediEnabled": false,Will be removed entirely. |
Sorry, something went wrong.
|
Hmm, I guess it's a known issue with the JSONC parser: microsoft/node-jsonc-parser#10 VS Code doesn't use this lib anymore as far as I know (in favor of some internal settings management), so it's difficult to do this sort of change here with files (rather than setting things via VS Code's APIs). |
Sorry, something went wrong.
There was a problem hiding this comment.
Per discussion with Karthik, I think we should remove the block of code that removes jediEnabled. Leaving jediEnabled isn't harmful as the setting is no longer read, and we won't unexpectedly modify a user's settings.json file. In a future release, we can clean up the jediEnabled setting if need be.
Mikhail Arkhipov (@MikhailArkhipov) could you remove that block?
Sorry, something went wrong.
|
Sure, although opener of #12429 wanted it removed I think. |
Sorry, something went wrong.
|
I think the main problem was that none of this code was active, so the effect was to not actually move people over to the languageServer setting. Whether or not the old setting is left behind I don't think changes that picture. |
Sorry, something went wrong.
|
Kudos, SonarCloud Quality Gate passed!
|
Sorry, something went wrong.
* Fix path * Actually fix settings * Add news * Add test * Format * Suppress 'jediEnabled' removal
* Actually fix user settings for `jediEnabled`. (#12433) * Fix path * Actually fix settings * Add news * Add test * Format * Suppress 'jediEnabled' removal * Prapare for point release Co-authored-by: Mikhail Arkhipov <mikhaila@microsoft.com>
| Back | FazBrowse Home | New Git URL |
For #12429
Add jediEnabled to the search inside content of settings files.
- [ ] Has telemetry for enhancements.
- [ ] Test plan is updated as appropriate.
- [ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
- [ ] The wiki is updated with any design decisions/details.