microsoft / microsoft/vscode-custom-data

Only seems to pick up custom data paths defined in 'settings.json' rather than 'code-workspace' files

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
240
Forks
95
PR merge metrics
No merged PRs in 30d

Description

Not sure if this is the correct location to place this, saw another user was directed here after submitting their issue directly to VSCode repo.

Essentially right now the 'customData' fields defined in VSCode are ignored when used inside a <workspace-name>.code-workspace file under the settings property however it does work when creating a .vscode/settings.json file.

This is somewhat confusing as the documentation states specifically it only currently works in workspace settings and I would expect the code-workspace files to be supported.

VSCode Version: 1.45.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue using customData in a .code-workspace file under settings, then compare it with the working .vscode/settings.json case in VS Code 1.45.1. Trace how each workspace-settings form is read and verify that customData is recognized in both formats without changing the documented behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.