[Feature Request] Create a Zed extension with VS Code extension feature parity
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
Start by locating the existing VS Code extension and use it as the reference for the requested Zed extension. Map each listed feature to its implementation and identify which Zed extension capabilities and tests would cover it. Done means delivering the listed .env and .env.schema features with parity to the VS Code extension; this is broad design and implementation work.
Written by the indexing model from the issue text.
Description
Description
Request to create a Zed editor extension that provides feature parity with the existing VS Code extension (@env-spec).
Motivation
Zed is an increasingly popular code editor, and many developers use it for working with .env files and environment variables. Having a native Zed extension would provide a better experience for Zed users.
Features to Implement
The Zed extension should include all features from the VS Code extension:
- Syntax Highlighting - Proper syntax highlighting for .env files and .env.schema files
- Comment Continuation - Smart comment continuation behavior
- Toggle Comment - Ability to toggle comments on/off
- Hover Info - Show hover information for variables
- IntelliSense/Autocomplete:
- Decorators autocomplete
- Type suggestions
- Variable resolvers
- Enum value suggestions
- Inline Diagnostics - Show inline diagnostic errors for schema validation
- Variable Resolution - Support for variable interpolation and references
Additional Information
The VS Code extension serves as the reference implementation. A Zed extension would follow the same patterns and provide the same level of functionality for Zed users.
- Dominant language
- TypeScript
- Stars
- 4.9k
- Forks
- 140
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 35
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dmno-dev/varlock
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dmno-dev/varlock#1279 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
dmno-dev/varlock#1100 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
dmno-dev/varlock#1278 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
dmno-dev/varlock#1275 · 1 comment ·
Maintainers usually reply within 1 day
-
core:varlock RFC
Difficulty 5/5 Over a week Newbie friendliness 28/100
dmno-dev/varlock#1258 · 1 comment ·
Maintainers usually reply within 1 day
All issues in dmno-dev/varlock
Similar issues
-
documentation good first issue roadmap
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
resend/react-email#3876 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
siyuan-note/siyuan#21324 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
himynameisdave/bsky-profanity-counter#59 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100