IssueRaiser

Shared properties in launch.json

## Search Terms launch.json, configuration, url ## Suggestion The ability to specify shared properties among launch configurations. Allowing properties to be inherited or specified in some common way while allowing overrides in individual entries would ease this situation greatly. ## Use Cases For example, I have many launch configurations that are identical except the URL. Management of changes then has to be propagated to each and every entry. Often a single launch.json can contain dozens of entries, and changing something simple but common like browser or other option must be done by search and replace. SNR itself is easy, but the repeated entries clutter up the launch.json and make spotting the actual differences when they exist other than URL more difficult. I fully understand this is a corner case and not relevant to a large audience, however it would be extremely helpful for those who do need it, and the implementation is small in scope. ## Examples Not too picky about actual implementation, but a possible idea is below. Multiple shared configs accessed by name would be even better to allow multiple default settings. ```json { "version": "0.2.0", "defaultConfiguration": [ "preLaunchTask": "build", "request": "launch", "sourceMaps": true, "port": 9222, "smartStep": true, "breakOnLoad": true, "webRoot": "${workspaceRoot}" ], "configurations": [ {

Posted by czhower on Jul 4, 2018, 10:28 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

ux (Other)

Shared properties in launch.json

czhowerJul 4, 2018, 10:28 PM

## Search Terms launch.json, configuration, url ## Suggestion The ability to specify shared properties among launch configurations. Allowing properties to be inherited or specified in some common way while allowing overrides in individual entries would ease this situation greatly. ## Use Cases For example, I have many launch configurations that are identical except the URL. Management of changes then has to be propagated to each and every entry. Often a single launch.json can contain dozens of entries, and changing something simple but common like browser or other option must be done by search and replace. SNR itself is easy, but the repeated entries clutter up the launch.json and make spotting the actual differences when they exist other than URL more difficult. I fully understand this is a corner case and not relevant to a large audience, however it would be extremely helpful for those who do need it, and the implementation is small in scope. ## Examples Not too picky about actual implementation, but a possible idea is below. Multiple shared configs accessed by name would be even better to allow multiple default settings. ```json { "version": "0.2.0", "defaultConfiguration": [ "preLaunchTask": "build", "request": "launch", "sourceMaps": true, "port": 9222, "smartStep": true, "breakOnLoad": true, "webRoot": "${workspaceRoot}" ], "configurations": [ {

Comments (0)

No comments yet. Start the discussion.

Comment on this issue