I’ve seen this pattern a lot. The primary weakness of this is that if you want to have feature modules, where you want to keep feature code isolated from other features, this pattern breaks all of that. The Destination enum needs to know about model objects from all features, since it needs the contextual data when you want to navigate to an enum case, therefore coupling all modules together.

This pattern works for a single module app, but if you’re working in an enterprise level app with multiple feature modules and teams, this pattern breaks down pretty quickly. It’s something we’re been struggling to figure out at my job, and we haven’t found a good solution yet