refactor: Sync "pixi workspace feature remove" behaviour with "pixi remove"#5129
Merged
Hofer-Julian merged 2 commits intoprefix-dev:mainfrom Dec 15, 2025
Merged
Conversation
Comment on lines
+2991
to
+2994
| // Remove non-existent feature should succeed | ||
| let result = manifest | ||
| .remove_feature(&FeatureName::from_str("nonexistent").unwrap()) | ||
| .unwrap(); |
Contributor
There was a problem hiding this comment.
Would be good to check that we log a warning there. No worries if that is hard to do.
Collaborator
Author
There was a problem hiding this comment.
From what I can tell, not directly doable, at least not without larger changes :/
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.
Description
Instead of
bail!when a feature doesn't exist, only print a warning, so the behavior is consistent with otherremovecommands.Checklist: