Thanks! (from divnix/std)

[blaggacao]

Looks like you solved a use case for https://github.com/divnix/std when we want to encourage repository maintainers to write higher quality repo scripts / tasks.

Let's keep track here if any feedback comes up.

cc @jmgilman

[blaggacao]

First one: flake? 😊

I really don't want to wrap legacy nix projects for the complexity it entails in std.

[blaggacao]

Second one: what have been your plans / ideas for positional arguments?

To keep a script interface simple and good dx, they are gold.

[lucasew]

Tbh I don't have that much idea about how to implement it, maybe something like how python's argparse works.

About the flake, I didn't used yet because I basically don't use external dependencies, but thinking about now it seems a good choice anyway.

I wanted to implement also the completion system but I really don't know how can I structure in a way that doesn't look very verbose.

[blaggacao]

completion system but I really don't know how can I structure in a way that doesn't look very verbose.

Was your plan to put them as a file im the right place next to the derivation alongside ./bin/scriptname?

Or where you rather concerned about the verbosity of the Nix code?

[lucasew]

Tbh I added the derivation only as a convenience feature. The idea is to generate the completion files as a target option, but this can be also exposed in that derivation.

[lucasew]

Verbose I am refering about the nix code the user would need to write to define the CLIs