Implement `etna-server`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 14
- Forks
- 2
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Currently, the only way to use etna is through the CLI, which makes it very hard to build a VSCode extension or any other interface. Most of the functionalities are isolated in the API so it should be easy to expose them through a REST API.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the existing API functionality and the CLI entry points, since the issue says most functionality is already isolated in the API. Define which capabilities the REST API must expose and how clients such as a VSCode extension will use them; done means those agreed capabilities are available through etna-server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100