devcontainer.json file's customizations of the project override feature's customizations

When there are the same vscode settings in both feature's and the project's devcontainer.json file, the project's customizations override the feature's. Is it possible to merge it instead of an override?

• devcontainer.json file at the features:

{
    "customizations": {
        "vscode": {
            "settings": {
                "files.associations": {
                    "LICENSE*": "plaintext"
                }
            }
        }
    }
}

• devcontainer.json file at the project:

{
    "customizations": {
        "vscode": {
            "settings": {
                "files.associations": {
                    "commit-msg-template": "git-commit"
                }
            }
        }
    }
}

Expected Result:

{
    "customizations": {
        "vscode": {
            "settings": {
                "files.associations": {
                    "LICENSE*": "plaintext",
                    "commit-msg-template": "git-commit"
                }
            }
        }
    }
}

Current Result:

{
    "customizations": {
        "vscode": {
            "settings": {
                "files.associations": {
                    "commit-msg-template": "git-commit"
                }
            }
        }
    }
}

Transferring to CLI repo

/cc @chrmarti Is this expected? I would have expected a merge of objects by default.

I have also ran into this snag, and was curious if there's any immediate plans to address it?

If not, could someone point me in the general location of where settings are handled in the code base and I could look at contributing a fix for this?

@chrmarti Any update about this bug?