pcapriotti / pcapriotti/optparse-applicative
Support for ospath/osstring
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 959
- Forks
- 123
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 1
Description
Can we have support for OsPath/OsString?
The idea of those types is to avoid converting from system (filepath) strings to String and back. But currently this is what happens if we want to construct an argument parser that returns OsPath.
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
No files or tests are named. Start by tracing how optparse-applicative currently converts system filepath strings when constructing an argument parser, then inspect the relevant parser and result types. Done means parsers can return OsPath or OsString without converting through String, with tests covering those return types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100