David Jennes

Hi @edwinveger, This is definitely something that could/should be added to SwiftGen. I haven't taken a look yet, but I assume that the structure/file format will be similar to our...

@AliSoftware proposed another idea, that we could add to this template (or an alternative one): ```swift protocol MyViewControllerTypedStoryboardSegue { func prepareSegueForEmbed(destination: EmbedDestinationVC) func prepareSegueForModal(destination: ModalDestionationVC) … func prepare(for segue: NSStoryboardSegue,...

To begin with: any and all suggestions are welcome! You could try mock-generating the code (manually) for one of your projects (or just 1 storyboard), and see if the generated...

This obviously needs a rebase, but before I continue dev. on this, a couple of issues: - How do we handle subclasses? Let's say `ClassA` has segues `S1` and `S2`,...

@AliSoftware This may better illustrate the situation:  Would lead to this code: ```swift class ClassA: NSViewController { enum TypedStoryboardSegue { case s1 case s2 init(_ segue: NSStoryboardSegue) { ......

Yeah, it's the `init` that fails, not the cases in the `switch`. Changing it to `ClassB.TypedStoryboardSegue` doesn't help, still ambiguous. We could prefix the `TypedStoryboardSegue` type with the class name,...

Keep in mind that this PR aggregates all segues over all storyboards for each type. Honestly? No idea. But as we have no information on what the class structure for...

The UserInfo thing's a good idea, as it's the only one we have access to. We actually have no idea what the level of inheritance is, that's in the swift...

Hi @MarcSteven, Thank you for your feedback. SwiftGen's current focus is a CLI interface, with the configuration mainly done via a configuration YAML file. We believe this is currently the...

What you have here is not a reserved keyword per se, but a collision with an existing type `Type`, that is the "metatype" for a given type (type-ception 😆). I'm...