Closed ewingjm closed 3 years ago
The obvious way to implement this would be a synchronous plug-in on the AddSolutionComponent
message that prevents you from adding a component to your solution if it already exists in a development solution. Unfortunately, that message is not enabled for SDK steps. It looks like we can register flows on create of a solutioncomponent
record, so that might be a good alternative if it's possible to register something synchronous on that.
Preventing developers from doing this is the end goal but a short-term solution that will be much quicker to implement would be to show a warning on the solution merge form when the development solution components have been detected in more than one solution (and show the names of the solutions). This then hopefully prevent those changes from being merged to master.
Closing this as I think #57 is the best we can do currently. Will reopen the issue if we're still seeing problems.
It is possible for multiple developers to modify the same components. This can result in incomplete changes being merged or development solutions failing to merge due to missing dependencies. There should be a mechanism by which developers check-out/check-in components into and from their development solutions.