Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add "include" directive to JSON #6502

Closed
kellytrinh opened this issue Jun 14, 2020 · 2 comments
Closed

Add "include" directive to JSON #6502

kellytrinh opened this issue Jun 14, 2020 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@kellytrinh
Copy link

Description of the new feature/enhancement

Suggest to add an #include or similar to the settings JSON.

I have in a bunch of profiles that launch SSH to connect to difference machines I am using. The list of machines is different from my laptop / devbox. Right now I cannot just take the settings JSON and put in another computer because it will mess up the profiles list.

This will allow me separate the profiles part (which may be computer specific) from the keybindings (which would be common).

Proposed technical implementation details (optional)

I have a common settings JSON that I can take between commons and add/remove profiles on a seperate file on each specific computer.
@kellytrinh kellytrinh added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 14, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 14, 2020
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #2303 for more discussion.

/dup #2303

@ghost
Copy link

ghost commented Jun 15, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jun 15, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 15, 2020
@zadjii-msft zadjii-msft mentioned this issue Sep 1, 2021
Closed
80 tasks
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kellytrinh @zadjii-msft