Expose Whale target and emit-kind capability queries
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start in src/cli.rs, where the Whale query is currently rejected, and trace the existing print interface and its human/JSON schemas. Implement the listed target and emit-kind queries, then verify aliases, invalid queries, and that LLVM defaults remain unchanged; done means Whale reports only Linux amd64 and IR, with check treated as validation and native outputs unavailable.
Written by the indexing model from the issue text.
Description
Motivation
wavec --whale print supported-targets is intentionally rejected by src/cli.rs even though the adapter has a definite one-target, one-output capability subset. Existing tooling cannot discover it through the established print interface.
Scope
Implement supported-targets/target-list and supported-emit-kinds using the existing human/JSON schemas. Advertise only Linux amd64 and IR; check is a validation mode, and native outputs are unavailable. Keep all other unsupported queries explicit and LLVM default behavior unchanged.
Difficulty: easy.
Completion criteria
- Return accurate human and JSON capabilities for Whale.
- Verify aliases and invalid query handling.
- Do not infer Whale capabilities from enabled LLVM targets.
- Dominant language
- Rust
- Stars
- 56
- Forks
- 21
- Avg merge
- 4h 44m
- Merged PRs (30d)
- 57
Getting set up
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 wavefnd/Wave
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement good first issue needs testing
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Distinguish Rust character literals from lifetimes in the spacing helperPossibly taken A pull request linked to this issue is open or already merged. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
area: config effort: S good first issue P3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ferenyl/azuredevopstui#63 ·
-
needs-triage O-Arm T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug CLI config mcp
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
yunaremaia/sandbox-ffi-layers#56 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
git-ai-project/git-ai#2434 ·
Maintainers usually reply within 1 day