Fix the incompatibility that occurred after updating urfave/cli (v3.0.0-alpha9.2)
#6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dearchap
approved these changes
Nov 4, 2024
|
@dearchap, could you please update the "Branch protection rules" in this repo?
|
|
Go ahead |
|
The new version should be |
|
I've released
@Juneezee do you have any suggestions on how to resolve this? |
|
@tarampampam just release 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After the changes in urfave/cli#1988 were released under
v3.0.0-alpha9.2, this package stopped working due to the removal of theGetValue() stringfunction from thecli.DocGenerationFlaginterface.This PR provides a workaround, which, while a bit rough, is functional and may serve as a temporary solution until a better approach is developed.
Closes #5