INCATools / INCATools/ontology-access-kit
OAK documentation and command line parsing should differentiate between TSV and CSV
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 198
- Forks
- 35
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
`runoak` help messages (for example `info`) may say that they can generate CSV, but I don't see how to change the delimiter to anything besides `\t` aka TSV
There are cases in which I would like CSV. Some LLM web interfaces won't attach TSVs. But I think it's more important to let people know that they may get TSV even though they asked for CSV.
Contributor guide
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 running the `runoak info` help and locating the command-line parsing and help text that describe CSV and TSV output. Check how delimiters are currently selected, then ensure the help accurately distinguishes CSV from TSV and explains the available delimiter behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100