The crux of the issue is that we have so many ways of linking a person to an event:
just booking the person (as interested, a teacher, etc) - is clean.
booked as the performer of an act... or as a member of a group that is the performer of the act... -- is messy, as the person to booking relationship is not part of the scheduling system.
When that problem -- person --> performer --> act --> scheduled show has a cleaner answer - then this can be refactored.
Pull request https://github.com/bethlakshmi/GBE2/pull/1243/files mentions that get_conflicts bounces around apps and could use a refactor - I don't want to forget this piece of tech debt.
The crux of the issue is that we have so many ways of linking a person to an event:
When that problem -- person --> performer --> act --> scheduled show has a cleaner answer - then this can be refactored.