-
-
Notifications
You must be signed in to change notification settings - Fork 112
Open
Description
We've been working on a lot over the past year, but haven't done a great job of releasing it to our users.
This Issue captures work towards a short-term checkpoint, where users can minimally
- install a self-updating
darklang
CLI exe - write a .dark script, and run it via the
darklang
exe- packages are provided via the live web-based package manager
- access and use our VS Code extension which wraps our LSP-based Language Server
- have a reasonable, if bare-bones, experience writing such a script
See companion issue #5265 for how this fits into our current goals.
We set these goals around a month ago in Notion, and here I'm attempting to represent them in a GitHub Issue instead
- installation and self-update of the CLI // ocean
- deal with MacOS code signing
- make execution/installation work on Windows
- parsing and pretty-printing
- otherwise, we won't be able to use it in the cli-hosted LSP server
- grammar to match more of our full language
- editor
- Update “Completions” request to return function names where relevant
- get context of what node you're on (could this be a function name?)
- extract the full word in focus (e.g.
List.a
) - provide function that takes "List.a" and suggests "List.append" along with other things (it might be possible for this to just return a list of all fns, and have the client filter it down appropriately)
- return relevant completions
- tidy marketplace page
- more completions -- type name, fn name, const name, genAI
- better
initialize
handling (respect the incoming request) - handle onHover
- view package sources
- Update “Completions” request to return function names where relevant
Metadata
Metadata
Assignees
Labels
No labels