WIP: upgrade urfave/cli to v2 #404
No reviewers
Labels
No Label
bug
build
ci/cd
contributing
design
documentation
duplicate
enhancement
help wanted
invalid
meta
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#404
Loading…
Reference in New Issue
No description provided.
Delete Branch "p4u1/abra:upgrade-cli"
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?
THIS IS VERY WIP!!!!
This is an attempt to fix a regression found by running the integration test suite.
The problem is with running the following:
This does not work properly with the old cli library
The main breaking change is a change in the order of flag and argument parsing (see here for details in the migration guide). This change is also what fixes the problem above.
@p4u1 Trying to dig into this now.
abra
users at large requested that we stay on v1 ofurfave
for the arg handling that it provides and I did the revert migration in0e688f1407
. Maybe handy if you DM me on matrix to figure this out together. Thanks for looking into it!coop-cloud/organising#336 seems relevant? Which involved dropping back to a point release of
urfave
? We could possibly attempt to pin there... am usinggit log -p --follow go.mod
to check the updates/commits...Thanks for the feedback! I open an issue to discuss this further coop-cloud/organising#581
@p4u1 given coop-cloud/docs.coopcloud.tech#256 (comment) I think it might be worth a look into how feasible it is to upgrade further into the alpha v3 which provides https://github.com/urfave/cli/pull/1568. this would allow us to specify some flags ("--chaos", "--debug", etc.) as global and can be passed in any "style"? This is a bit of a long shot but might be nicer than "patch to re-order flags" and we could also help upstream fix stuff as we go... whatcha reckon?
Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.