Currently the GraphMerger only has sync merge versions. Which work perfectly fine when the BO only has sync rules.
To make the merger more async friendly it should get three new async versions of these public methods:
The new async versions must use CheckRulesAsync where the current version is using the sync method.
The current sync version must work as before.
Furthermore it should be checked where the sync merge methods are used within the framework.
If and only if the method using the merge method is already async it should be changed to the new async api.
Currently the
GraphMerger
only has sync merge versions. Which work perfectly fine when the BO only has sync rules. To make the merger more async friendly it should get three new async versions of these public methods:The new async versions must use
CheckRulesAsync
where the current version is using the sync method. The current sync version must work as before. Furthermore it should be checked where the sync merge methods are used within the framework. If and only if the method using the merge method is already async it should be changed to the new async api.