devcontainers / devcontainers/devcontainers.github.io
Add "Supported Distros" column to Features table (and consider adding to spec)
- Linguagem predominante
- HTML
- Estrelas
- 207
- Forks
- 434
- Merge médio
- 2d 7h
- PRs com merge (30d)
- 2
Descrição
I've encountered situations where I want to add a Feature to a devcontainer configuration, only to discover later that it supports only certain distros or package managers. This typically becomes apparent only at build time, leading to wasted effort.
To improve the experience, I'd like to suggest adding a "Supported Distros" column to the Features table at https://containers.dev/features. Displaying this information up front (rather than having it buried in project READMEs) would make it easier to determine whether a Feature can be used with a specific base image or distro, saving time and reducing confusion.
Since the spec already acknowledges this limitation in the [docs](https://containers.dev/implementors/features/):
> Note: While Features may be installed on top of any base image, the implementation of a Feature might restrict it to a subset of possible base images. For example, some Features may be authored to work with a certain Linux distro (e.g. debian-based images that use the apt package manager).
It might be worth adding a `supportedDistros` property to the `devcontainer-feature.json` spec itself. This would improve discoverability, allow the documentation to be auto-generated and ensure distro compatibility is consistently documented across all Features.
Thanks for considering this enhancement!
Guia de contribuição
Direção de pesquisa
Comece pela tabela de Features em https://containers.dev/features e pelas notas de implementação de Features em https://containers.dev/implementors/features/. Em seguida, localize a especificação de devcontainer-feature.json e determine como as informações sobre as distros compatíveis devem ser representadas e exibidas na tabela. Considera-se concluído quando as informações de compatibilidade solicitadas estiverem documentadas de forma consistente e a alteração na especificação estiver incluída, caso seja aceita.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- html, json
- Domínio
- documentation
- Tipo de issue
- Funcionalidade
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 45/100