Add check for unique chaincode names across channels #528
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.
fixes : issue#228
This pull request introduces a new validation to ensure that chaincode names are unique across different channels. It includes changes to both the test suite and the core configuration extension logic.
New validation for unique chaincode names:
e2e/fabloCommands.test.ts
: Added a test case to check for duplicate chaincode names across different channels, ensuring that the validation throws an error when duplicates are found.src/extend-config/extendChaincodesConfig.ts
: Introduced thecheckUniqueChaincodeNames
function to validate that all chaincode names are unique within the provided configuration. This function is called within theextendChaincodesConfig
function.Integration of the new validation:
src/extend-config/extendConfig.ts
: Imported thecheckUniqueChaincodeNames
function and integrated it into theextendConfig
function to ensure chaincode names are checked for uniqueness during the configuration extension process.