The argument ordering question #11
Labels
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/go-abra#11
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I was trying to wire up urfave to use
abra recipe <recipe> version
ordering but as I have discovered, I have no idea how to do this.@3wordchant mentioned a discussion with @roxxers about this and I see some rumours of an outcome in coop-cloud/abra#189.
I am personally fine with moving to
abra recipe version <recipe>
ordering and moving all non-global flags/args to the end of the command order (as I believe @knoflook was suggesting?).I am wary of moving into "making new things" in this port while we're still trying to get to feature parity but this one seems like a fine shortcut to take since parsing the original ordering looks tricky & hard to do.
Thoughts?
Some logs attached...