devcontainers / devcontainers/spec

Should the namespace of `customizations` be more standardized?

Open
#262 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
5.7k
Forks
496
PR merge metrics
No merged PRs in 30d

Description

Currently, customizations are namespaced by arbitrary product names. The only two I've seen in wide-use are `vscode` and `codespaces`, which makes sense as those are the only two widely used implementations of devcontainers.

As the spec is picking up steam, it may be worth considering changing these keys to use [reverse domain name notation](https://en.wikipedia.org/wiki/Reverse_domain_name_notation). Implementing tools would continue to support the original names for the foreseeable future, but could map the legacy name to the proper name and potentially print a warning at build time at some point in the future if the customization namespace does not look like a reverse domain, with extra flavor for well-known names.

Thoughts? If there's interest I could write it up as an actual proposal.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.