Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: refactor pixi::consts and pixi::config into separate crates #1684

Merged
merged 9 commits into from
Jul 29, 2024

Conversation

tdejager
Copy link
Contributor

Refactors these types into their seperate crates.

I've kept consts in the const namespace, and made the use of it consistent, i.e never import from const directly but always append with the namespace. I've kept the const module for that reason as I like to avoid mod as other_mod whenever possible.

Config I've also put in it seperate crate, this could use a subsequent refactor because the lib file is much too big for my taste, I think that refactor is a bit overdue tbh.

I've kept the refactor limited to moving of the types, and have not changed anything significant, I believe the review would have been impossible otherwise.

cc @wolfv

crates/pixi_config/src/consts.rs Outdated Show resolved Hide resolved
crates/pixi_consts/Cargo.toml Outdated Show resolved Hide resolved
src/project/environment.rs Outdated Show resolved Hide resolved
crates/pixi_config/src/lib.rs Outdated Show resolved Hide resolved
@wolfv wolfv changed the title refactor: refactor pixi::consts and pixi::config into seperate crates refactor: refactor pixi::consts and pixi::config into separate crates Jul 29, 2024
@tdejager tdejager enabled auto-merge (squash) July 29, 2024 14:54
@tdejager tdejager merged commit 5295190 into prefix-dev:main Jul 29, 2024
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants