Josh Spicer

toying around with a simple example repo: https://github.com/joshspicer/extends

I'd suggest renaming `alias` to something less neutral - perhaps a `deprecatedIds` array that we will still publish to, but that we can handle appropriately in downstream tooling. What do...

> If we decide to support renaming across namespaces I think a good first pass for this would be re-aliasing inside a single namespace. The property could even just accept...

+1 to this. Below is just some spitballing, but an idea i've been tossing around is the concept of _library Features_. They cannot be referenced directly in a devcontainer.json, but...

I like this - will clean up our templates a bit and improve readability.

Hey @aservedio! That functionality is not clearly documented, but indeed built into the CLI as the `templates apply` command. We use the CLI in the extension to directly apply the...

@chrmarti - are you suggesting features that look like this? ```jsonc "features": { "devcontainers/features/[email protected]" : { "version": [16, 14, latest] } ``` or equivalently with the shorthand that implies "version"...

> Does the current spec allow specifying the same feature with different versions in the key with the current object syntax, such as the following? Yes, given the object syntax...

For the `dotnet` feature, I can imagine users wanting to install `dotnet` twice with the following options. These are the existing options today, and two plausible ways a user could...

@Chuxel I agree we may be getting side-tracked. I added a new issue to address (1) in your comment: https://github.com/devcontainers/spec/issues/57 I want this proposal to focus on (2), particularly for...