fix: inner_configure: Check Config::OnlyFetchMvbox before MvboxMove for multi-transport (#7637) #7641
+6
−4
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
…or multi-transport (#7637) `Config::OnlyFetchMvbox` should be checked before `MvboxMove` because the latter makes no sense in presense of `OnlyFetchMvbox` and even grayed out in the UIs in this case. Otherwise users will see an error mentioning the wrong setting.
r10s
approved these changes
Dec 22, 2025
Contributor
r10s
left a comment
r10s
left a comment
There was a problem hiding this comment.
makes sense.
really looking forward to get rid of these options alltogether :)
Simon-Laux
approved these changes
Dec 22, 2025
link2xt
approved these changes
Dec 23, 2025
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.
Config::OnlyFetchMvboxshould be checked beforeMvboxMovebecause the latter makes no sense in presense ofOnlyFetchMvboxand even grayed out in the UIs in this case. Otherwise users will see an error mentioning the wrong setting.Fix #7637