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.

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

Organize profiles by folder #5850

Closed
jdhitsolutions opened this issue May 11, 2020 · 2 comments
Closed

Organize profiles by folder #5850

jdhitsolutions opened this issue May 11, 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

@jdhitsolutions
Copy link

jdhitsolutions commented May 11, 2020

I may be an edge user or perhaps just an enthusiastic user but I would like to have a way to organize my profiles into "folders" or some type of hierarchy. I currently have 11 profiles and I know this will increase. It would be very helpful to have a way to organize the layout.

Somehow the json would need on outer folder element. Maybe something like this:

{
    "folder": "Foo",
    "list": [
        {
            "guid": "{a3a2e83a-884a-5379-baa8-16f193a13b21}",
            "hidden": false,
            "name": "PowerShell 7 Preview",
            "source": "Windows.Terminal.PowershellCore"
        },
        {
            "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
            "hidden": true,
            "useAcrylic": false,
            "name": "Azure Cloud Shell",
            "source": "Windows.Terminal.Azure"
        }
    ]
}

I suppose another way might be to extend the schema and include a new element that indicates the folder.

{
    "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
    "hidden": true,
    "useAcrylic": false,
    "name": "Azure Cloud Shell",
    "source": "Windows.Terminal.Azure",
    "folder":"Foo"
}

The application would build a display based on the folder setting.

I realize this is a long term request

@jdhitsolutions jdhitsolutions added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 11, 2020
@ghost ghost added 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 May 11, 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 #1571 for more discussion.

/dup #1571

@ghost
Copy link

ghost commented May 11, 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 May 11, 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 May 11, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

2 participants