Implemented
0
Dev container fails to start with features that have array-valued options
Source: zed-industries/zed#63978 · opened by @langalex
Reproduction steps Create a .devcontainer/devcontainer.json with a feature that accepts array options, for example: 2. Open the project in Zed and select "Open in Container" 3. Observe the error: Root Cause: Zed's FeatureOptionValue enum in crates/dev_container/src/devcontainer_json.rs is defined with only Bool(bool) and String(String) variants. When deserializing feature options, any array or object value fails to match these variants, causing the untagged enum deserialization to fail. Current vs. Expected behavior Zed should support all valid devcontainer feature option types as per the [Dev Container Features spec]( including: • Booleans • Strings • Numbers • Arrays • Objects • Null Zed version and system specs Zed: v1.18.0+stable (Zed) OS: Linux Wayland fedora-asahi-remix 43 Memory: 30.9 GiB Architecture: aarch64 GPU: Apple M1 Pro (G13S C0) || Honeykrisp || Mesa 25.3.6 Attach Zed log file <details><summary&…
No pledges yet. Be the first to back this.
Comments
Similar requests
Make avatar fallback to displaying initials if fetching the GitHub user's photo fails
0 votes · 0 comments
Ability to copy/paste files from the system file manager
99 votes · 0 comments
Separate `file_scan_exclusions` into distinct options for scan, search and tree exlusions
88 votes · 0 comments
Support bun as drop in replacement for npm/node
43 votes · 0 comments
Advanced Options in Context Menus
0 votes · 0 comments
No comments yet.