Deprecated. . .

[zhouxinghong]

Deprecated. . .

[vscodenpa]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.87.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[gjsjohnmurray]

/duplicate

[vscodenpa]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

[gjsjohnmurray]

@zhouxinghong you yourself have made clear that this is a duplicate of #204061

That issue has not (yet) been locked, so you can continue to comment on it there if you wish. Several of us have repeatedly tried to get clarity from you about what behavioural change in VS Code you are unhappy with.

From my perspective (I am not a member of the core team) the outcome of the responses by domain lead members of the core team to the many duplicates you have apparently posted is:

1. Occasionally it becomes necessary to migrate existing values in settings.json etc files to become different values (schema evolution). I suggest you get used to this, as I doubt it will never happen again.
2. An open issue remains about how the settings migration mechanism apparently deletes user-added // comments. There is currently no core team resource available to investigate / address this, but the team is open to considering a PR from the community.

Hoping you will understand and accept the situation.