chore(cli): kill subnet — zero subnet/Subnet/SUBNET in cli#41
Merged
Conversation
Final lux sweep. Five small touches: cmd/networkcmd/start_local.go "subnet creation" → "chain creation" (comment) cmd/explorecmd/explore.go "or subnet name" → "or chain name" (flag help) pkg/plugins/luxdConfig_test.go test fixture: testSubNet → testChain, subNetId000 → chainId000 pkg/mpc/deploy.go AWSSubnet → AWSNet (Go field + json tag) The AWS field rename is Go-side only. AWS itself still calls the resource a subnet on the wire; our config field carries the canonical name without taking a dependency on AWS API verbiage. Build clean.
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
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.
Final lux sweep. 5 small touches across 4 files. AWS field AWSSubnet → AWSNet (Go-side only; AWS wire stays). Build clean.