Support for ospath/osstring

Open
#491 14 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
haskell
Domain
cli

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.

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.

Dominant language
Haskell
Stars
957
Forks
124
PR merge metrics
No merged PRs in 30d

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 pcapriotti/optparse-applicative

All issues in pcapriotti/optparse-applicative

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.