This PR migrates the V-SUM to use UUIDs within its changes while preserving hierarchical IDs for any view (adapting to https://github.com/vitruv-tools/Vitruv-Change/pull/47). The conversion from HID-based changes to UUID-based ones happens in the IdentityMappingViewType.
Adapt to API changes
Rewrite ResourceRepositoryImpl to use one change recorder instead of multiple ones. I must admit that I don't fully recall why I added this change. I guess it was before I separated change recording and UUID assignment as sharing a UUID resolver over multiple recorders might be problematic. Anyways, it does not change functionality and makes the code easier to read, thus I would suggest to keep that change.
There is one code duplication regarding assigning hierarchical IDs to changes. As we should refactor hierarchical ID and UUID resolvers to be hidden behind the same IDResolver interface I postponed refactoring this code smell to when such interface exists. I would document it accordingly in an issue.
This PR migrates the V-SUM to use UUIDs within its changes while preserving hierarchical IDs for any view (adapting to https://github.com/vitruv-tools/Vitruv-Change/pull/47). The conversion from HID-based changes to UUID-based ones happens in the
IdentityMappingViewType.ResourceRepositoryImplto use one change recorder instead of multiple ones. I must admit that I don't fully recall why I added this change. I guess it was before I separated change recording and UUID assignment as sharing a UUID resolver over multiple recorders might be problematic. Anyways, it does not change functionality and makes the code easier to read, thus I would suggest to keep that change.There is one code duplication regarding assigning hierarchical IDs to changes. As we should refactor hierarchical ID and UUID resolvers to be hidden behind the same
IDResolverinterface I postponed refactoring this code smell to when such interface exists. I would document it accordingly in an issue.