zowe.config.user.json not being leveraged properly

Describe the bug

Properties in zowe.config.user.json are not being merged with like-named profiles in zowe.config.json. In this situation, Zowe Explorer fails to start, and I receive the following error:

To Reproduce

Steps to reproduce the behavior:

1. Add this content to your global zowe.config.json:

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "zosmf": {
            "profiles": {
                "lpar1": {"type": "zosmf","properties": {"host": "myhost.com"}}
            },
            "properties": {
                "port": 443
            }
        },
        "base": {
            "type": "base",
            "properties": {
                "rejectUnauthorized": false
            }
        }
    },
    "defaults": {
        "zosmf": "zosmf.lpar1",
        "base": "base"
        },
    "autoStore": false
}

1. Add this content to your global zowe.config.user.json:

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "zosmf-working": {
            "profiles": {
                "lpar1": {"type": "zosmf","properties": {"user": "myuser"}}
            },
            "properties": {
            }
        }
    },
    "defaults": {
        "zosmf": "zosmf.lpar1"
    },
    "autoStore": false
}

1. Launch VSCode and note that everything loads properly
2. In your global zowe.config.user.json, change zosmf-working to just zosmf
3. Relaunch VS Code and note this error on startup:

Expected behavior

Zowe Explorer starts up and properties of like-named profiles in zowe.config.user.json override values in the zowe.config.json.

Desktop (please complete the following information):

• OS: Windows 10
• Zowe Explorer Version: v2.0.0-next.202112161700

[zFernand0]

That’s right. One could also pull that branch and run the extension from the debugger in order to verify the functionality 😋

[crawr]

Upon further investigation, I found what seems like a bug in loadSchema in these lines:

Since the profile.profLoc.osLoc contains an array of 2 items, the schemaMapKey looks like:

and because mProfileSchemaCache looks like:

it is not able to find the correct schema and returns null. This causes the error message.