Multi-layered feature metadata?

In https://github.com/devcontainers/images, it seems that the builds include customization for vscode written in devcontainer.json. How is this intended to work? So far, when I do a build on hand based on these images, the settings for vscode defined in https://github.com/devcontainers/images do not seem to be reflected in the container on hand, is this the intended behavior? Perhaps I am missing a spec, but I am wondering which settings up to which are normal to be reflected in the container at hand.

In other words, while it is often convenient to have the settings for vscode defined in upstream reflected at hand, as it eliminates the need to write most of the devcontainer.json at hand. But without the option to remove metadata defined by upstream, we may suffer from unnecessary settings defined upstream. (Similar to user frustration with not being able to remove EXPOSE or VOLUME from upstream Dockerfiles)

[chrmarti]

This spec proposal has additional details: https://github.com/devcontainers/spec/blob/main/proposals/image-metadata.md

[eitsupi]

Yeah, I created a template with the same strategy and it seems to be working well. https://github.com/rocker-org/devcontainer-templates/blob/6c46be9b038d42cd4c54f1f0646dfca13b3a60e3/src/r-ver/.devcontainer/devcontainer.json

Perhaps my version of VSCode Dev Container at the time was older and not working well, thanks!