Josh Spicer

This is the current interface for the `python` feature 

@Alegrowin There's no workaround within the spec today to install the same Feature twice. We're exploring changing this soon with the introduction of composite/dependencies, but this exact functionality in on...

For option (B), we'd want to give hints in our `devcontainer-feature.json` to implementing UX tools that this is an array. The tooling could then simply write the set of chosen...

Thinking about the implementation side, it seems most natural to me (since the default [$IFS](https://www.baeldung.com/linux/ifs-shell-variable#ifs-variable-and-its-default-values) value in bash includes whitespace). A for loop going over the value would look like:...

@chrmarti - all sounds good to me!

Hey, @johnnyreilly! With the current [Features spec](https://containers.dev/implementors/features/) as it stands today, the default behavior is that the implementing tool decides the installation order. Our current goal with Features is that...

> Assuming features are named reasonably, what I would love is to have installsAfter: "*python*" Using a regex is an interesting idea. It would be assuming a lot, but I...

Hey @danielbraun89 - I've been taking a lot of inspiration from your excellent work on dependencies in `devcontainers-contrib`. I'm curious if you have any learnings you'd like to share -...

An implementation based on https://github.com/devcontainers/spec/pull/234 has been merged and shipped with version 0.44.0 of the CLI. GitHub Codespaces and the Dev Containers extension will pick up the changes in the...

> Just to clarify, Dockerfiles are still fully supported These docs will be helpful if you'd like to augment our existing templates with a Dockerfile. https://containers.dev/implementors/json_reference/#image-specific