Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`connection list | view | create | edit | delete`

Open
#34 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
cli

Research direction

Start with epic #21 and source.coop#593, since this issue depends on the API endpoints for connections, which may not exist yet. The CLI should only send requests and print the API's field_errors, with no local validation. Done means each of the list, view, create, edit and delete subcommands works against the API, and a CLI path is added under docs/using-source/ in docs.source.coop.

Written by the indexing model from the issue text.

Description

enhancement

Manage data connections.

Depends on source-cooperative/source.coop#593.

Part of #21. Per the epic, the CLI validates nothing itself: it sends the request and shows the API's field_errors. Add a CLI path to docs.source.coop docs/using-source/ wherever this flow gets one.

Dominant language
Rust
Stars
1
Forks
0
Avg merge
18h 52m
Merged PRs (30d)
19

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from source-cooperative/source-coop-cli

All issues in source-cooperative/source-coop-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.