The current strategies work well to merge two versions. In some use cases, there is a need to merge multiple versions at the same time to get the final version.
For example, merging a startup's funding amount from different media sources.
version = v_techcrunch
{
"name": "Coinbase",
"funding": "$200M"
}
version = v_crunchbase
{
"name": "Coinbase",
"funding": "$80M"
}
version = v_angellist
{
"name": "Coinbase",
"funding": "$120M"
}
final_version
{
"name": "Coinbase",
"funding": "$200M" <--- from v_techcrunch version
}
Here, it needs to be merged based on how recent and accurate data each media sources have. Like TechCrunch will have the latest data of startup's funding compare to Crunchbase and AngelList.
Some ideas of additional merge strategy
priorityMerge: merge based on the priority list
timebasedMerge: merge based on how recent data is
I am taking inspiration from all contributes of this repo who did great work, to make something similar to that supports the merger of multiple versions.
The current strategies work well to merge two versions. In some use cases, there is a need to merge multiple versions at the same time to get the final version.
For example, merging a startup's funding amount from different media sources.
Here, it needs to be merged based on how recent and accurate data each media sources have. Like TechCrunch will have the latest data of startup's funding compare to Crunchbase and AngelList.
Some ideas of additional merge strategy
I am taking inspiration from all contributes of this repo who did great work, to make something similar to that supports the merger of multiple versions.
Cheers