Rename subnet -> blockchain in Config #212
Merged
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.
Why this should be merged
Fixes #170
The application requires unique Blockchain IDs in the configuration, but the naming suggests that Subnets also need to be unique. Subnets can contain multiple blockchains, in which case there would need to be multiple entries in
SourceSubnets
andDestinationSubnets
with the same subnet ID.How this works
Renames
SourceSubnet
toSourceBlockchain
andDestinationSubnet
toDestinationBlockchain
in the configuration.How this was tested
CI
How is this documented
Updated README