chore: mark NetworkConfigs non-exhaustive
#12036
Closed
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
onbjerg
requested review from
0xrusowsky,
DaniPopes,
grandizzy,
mattsse and
zerosnacks
as code owners
auto-merge was automatically disabled
October 9, 2025 10:16
Pull request was closed
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Motivation
Ideally
NetworkConfigsis an enum, but for now we're stuck with the--<network>flag paradigm. Ideally, it would be something like--flavor <network>or--network <network>, because it is a logic error to have multiple networks enabled at the same time.Solution
Given we're stuck with
--<network>, we should markNetworkConfigsnon-exhaustive to prevent constructing the struct directly, and to prevent destructuring it without handling future networks.PR Checklist