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

Shared gh-style conveniences: --json/--jq, TTY tables, --web, prompts

Open
  • Is something wrong?
#28 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
openapi, rust
Domain
cli

Research direction

The issue names no existing source files; start from the first command group it mentions (auth status or product) and the published OpenAPI document at source.coop/api/openapi. Done means the shared flags, TTY table, shorthand and prompts work on that first command, with the API's field_errors shown as-is, and a CLI path added under docs.source.coop docs/using-source/. Design decisions on flag and prompt behaviour should be settled with maintainers before coding.

Written by the indexing model from the issue text.

Description

enhancement

Cross-cutting behaviour every command group uses. Land it alongside the first dedicated command (likely auth status or product).

  • --json <fields> and --jq <expr> on every read; a table when stdout is a TTY.
  • --web opens the matching source.coop page.
  • account/product shorthand, e.g. source-coop product view radiant/landcover.
  • Interactive prompts for missing required arguments when a TTY is attached; none otherwise (fail with a usage error).
  • --help text and any generated request types come from the published OpenAPI document at source.coop/api/openapi.

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.