Store unique origins on entries (i.e., buckets) in content aggregate
The content aggregator organizes files that it collects by component name and version. These collections are referred to as buckets. A bucket may contain files that were sourced from different origins (i.e., different git references or start paths). In order for an extension to get a list of all the unique origins, it must iterate through all the files in all the buckets and build a set from the src.origin
property on each file. If a bucket has no files, it's impossible to know its origin.
It would be helpful if the unique origins were stored on each bucket. Origins are natural unique between buckets.
With this change, an extension will be able to do the following:
for (const bucket of contentAggregate) {
for (const origin of bucket.origins) {
console.dir(origin)
}
}