Remove vg explode#4945
Merged
Merged
Conversation
adamnovak
reviewed
Jun 30, 2026
Co-authored-by: Adam Novak <[email protected]>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changelog Entry
To be copied to the draft changelog by merger:
vg explodeis removedDescription
Resolves #2855, from over six years ago, which is frankly a ridiculous amount of time to get rid of a subcommand that, when run, does nothing but error and tell you to do something else.
And! About "tell you to do something else". I have added a simple map lookup for removed subcommands. If we think that there should be a warning message printed when you try to use something we've axed, now we can have that message printed even in the absence of the subcommand.