We are currently looking to get a better setup for asynchronous development in Qlik Compose. Until now we have been a team of 2 developers, so the task of developing has been manageable by communication the 2 in between. But we are looking into getting more developers on board and are now looking for a way to effectively control our development cycle.
We have looked into a setup with a Git repository, where each developer would have their own branch of the main project for development, and then merge their changes into the main project manually. In this we see an issue in the merge of the project JSON file, as the Entity Ids would conflict between the main project and the separate development projects, and thus leave a big amount of manual work when merging.
Alternatively, we have talked with about splitting our Compose project into smaller projects, based on business areas. But we have a lot of entangled transformations, so this is not a viable option.
Does anybody have any recommendations for best practice in this situation, with multiple developers in Qlik Compose?