Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No arg package ? #1

Open
dearchap opened this issue Dec 28, 2021 · 3 comments
Open

No arg package ? #1

dearchap opened this issue Dec 28, 2021 · 3 comments

Comments

@dearchap
Copy link

The README shows the command.WithArgs and arg.New . Are these available in a branch that you havent pushed ? If its not available I was wondering if I can work on doing it. 😃

@rliebz
Copy link
Owner

rliebz commented Dec 30, 2021

Hey @dearchap, thanks for the interest!

This is a toy project I had a couple years back, and part of that was practicing documentation-driven development. So I'll definitely double down on the line from the README:

Warning: Clip is currently incomplete software and should not yet be used by anyone.

At this point, it's probably more likely that this never ends up anywhere than that it does, so picking up new work here might be akin to throwing code into the void 😅

That said, I pushed up the very rudimentary work I had but hadn't checked in—it's a partial implementation of WithArgs and no support for WithArg. There's a good chance this isn't the right direction, but if you're interested: https://github.com/rliebz/clip/tree/args

@dearchap
Copy link
Author

dearchap commented Dec 30, 2021 via email

@rliebz
Copy link
Owner

rliebz commented Jan 4, 2022

Unfortunately I'm not going to be able to give dedicated support time to this repo any time soon.

If I ever do pick it up:

  1. Seems reasonable
  2. Also seems reasonable
  3. First-class support doesn't seem like a good fit for the repo. Definitely want to support this kind of feature, and ideally a user could combine the two pretty easily, but adding a dependency for that functionality is a non-starter
  4. Absolutely. Curious to see if there aren't ways generics can make this more straightforward for the caller as well

Definitely feel free to fork or use patterns from the repo if it helps. It's just not something I can personally commit to supporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants