feat: Add new pixi-api crate for an unified pixi api (WIP) #4235
Conversation
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
haecker-felix
changed the title
|
For the unneeded dependencies, you can use https://github.com/bnjbvr/cargo-machete |
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.
Right now it "just" moves most of the logic from
pixito a separatepixi-apicrate, so it can be consumed by different modules / binaries (eg. cli, integration tests, gui, ...).I'm not 100% sure yet if this approach will lead to something useful.
TODO:
pixiand what should get moved topixi-apiPixiControland the builder patterns)pixiCargo.toml - probably has a dozen of no longer needed dependencies now