UX: How to handle the deletion of default profiles?

[zFernand0]

After the implementation of #3037 is complete, we may need to decide what to do when profiles are deleted.

Here are some options:

• Leave the deleted profile set as default (i.e. do nothing)
• Set the default profile to undefined or null
• Prompt the user for a new default profile of that type (zosmf, zftp, ...)

Please not that there may be nested profile which also happen to be defaults.

Expand this section to see an example config file

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "LPAR1": {
            "type": "zosmf",
            "properties": {
                "host": "my.company.net",
                "port": 443
            },
            "profiles": {
                "zftp": {
                    "type": "zftp",
                    "properties": {
                        "port": 21
                    }
                }
            },
            "secure": []
        },
        "base": {
            "type": "base",
            "properties": {},
            "secure": [
                "user",
                "password"
            ]
        }
    },
    "defaults": {
        "zosmf": "LPAR1",
        "zftp": "LPAR1.zftp",
        "base": "base"
    },
    "autoStore": true
}

---

Created a quick PoC of how the option could work if we decide to keep it: feat/delete-v2-profiles

Originally posted by @t1m0thyj in #3037 (comment)

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[t1m0thyj]

No longer applicable since we decided to remove the Delete Profile option from quickpick.

We should consider these options when creating a visual config editor 😋 #3336