-
Notifications
You must be signed in to change notification settings - Fork 495
pixi config unset should not error on unknown keys #5672
Copy link
Copy link
Open
Labels
approvedThe Pixi maintainers welcome contributions to solve this issue or implement the feature/bugfix.The Pixi maintainers welcome contributions to solve this issue or implement the feature/bugfix.configurationIssue related to configuration of workspace or global behaviorIssue related to configuration of workspace or global behaviorenhancementNew featuresNew featuresgood first issueGood for newcomersGood for newcomershelp wantedMaintainers would like community inputMaintainers would like community input
Metadata
Metadata
Assignees
Labels
approvedThe Pixi maintainers welcome contributions to solve this issue or implement the feature/bugfix.The Pixi maintainers welcome contributions to solve this issue or implement the feature/bugfix.configurationIssue related to configuration of workspace or global behaviorIssue related to configuration of workspace or global behaviorenhancementNew featuresNew featuresgood first issueGood for newcomersGood for newcomershelp wantedMaintainers would like community inputMaintainers would like community input
Problem description
repodata-config.disable-jlapwas recently removed from the config struct. This resulted in a warning about that value not existing.That's all fine but you should be able to use
pixi config unsetto remove unknown values from that config.E.g.: this should work IMO
It would be best if you can use the
pixi config unsetto remove any type of TOML value from the config files. Also because our warnings contain the exact config file path it would be great ifpixi configcould accept paths to those files to eliminate issues where the user doesn't know which config level e.g.--global--localetc.