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

maint: Remove PrefixData::load #3318

Merged
merged 1 commit into from
Jun 13, 2024

Conversation

jjerphan
Copy link
Member

Merge its content within PrefixData::PrefixData.

@jjerphan jjerphan marked this pull request as ready for review June 11, 2024 09:44
Merge its content within `PrefixData::PrefixData`.

Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
@jjerphan jjerphan force-pushed the maint-remove-PrefixData-load branch from 5f72e84 to 24f011a Compare June 11, 2024 10:55
@JohanMabille JohanMabille added the release::enhancements For enhancements PRs or implementing features label Jun 13, 2024
@JohanMabille JohanMabille merged commit 0793fad into mamba-org:main Jun 13, 2024
32 of 33 checks passed
@jjerphan jjerphan deleted the maint-remove-PrefixData-load branch June 13, 2024 14:17
@Hind-M
Copy link
Member

Hind-M commented Jun 13, 2024

We should remove this as well.

@jjerphan
Copy link
Member Author

Yes, I probably should have kept this PR in Draft.

There's the same pattern with SubdirData:

SubdirData::load(MultiPackageCache& caches, ChannelContext& channel_context, const specs::Channel& channel)

@Hind-M
Copy link
Member

Hind-M commented Jun 13, 2024

IMHO, I think we should keep them all, since it's kind of separating the logic and it's easier to read (better that blocks of code at once). And it's not like it's defined somewhere far away in the codebase or in another file... It's just the method right below...

@jjerphan
Copy link
Member Author

PrefixData::load only was called once in the constructor, in that case I think it would have made sense to merge it to prevent any misuse. No strong opinion.

Do you propose reverting the merge commit?

@Hind-M
Copy link
Member

Hind-M commented Jun 13, 2024

No strong opinion either, I was just expressing mine ^^

Do you propose reverting the merge commit?

Either that or removing the leftover in the header. But for SubdirData, I would keep it the way it is.

@jjerphan
Copy link
Member Author

I just have opened #3325.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release::enhancements For enhancements PRs or implementing features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants