[PubgrubTests] Handle duplicate product keys in DependencyGraphBuilder.serve
#3564
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.
This PR fixes 2 places where
DependencyGraphBuilder.servemishandlesdependencieswith duplicate keys (products).One of the callers of the function passes in a dictionary literal with duplicate keys. Although the logic in this function suggests that duplicate keys are allowed,
TSCBasic.OrderedDictionarypreserves only the final of all duplicate keys' values in a dictionary literal. In addition, with Adopt Swift Collections'OrderedSetandOrderedDictionary#3533, Swift Collections'OrderedDictionarytraps on duplicate keys.KeyValuePairsseems like the right replacement that allows duplicate keys.Because of the duplicate keys, when
dependenciesare iterated, the sameproductcan appear more than once, each time with possibly differentfilteredDependencies. In each iteration, thefilteredDependenciesassociated with theproductis mapped topackageDependencies, which is then assigned to the value in a different dictionary keyed by the sameproduct, overriding any existing value from a possible previous assignment. Changing the assignment to an appending operation preserves all previous values.