Jorge Revuelta

I think this can be reopened and we can work on finding a deterministic solution to generate interfaces for projects and SPM modules. Thoughts?

I think what neither of those do is generate the whole module doc, as happen when you click over an `import XXXX` statement , this gets tricky with SPM modules...

A good example of what I'm trying to achieve in a more automated way is in here: https://github.com/bq/mini-swift/blob/master/docs/Mini.swift

I've created https://github.com/minuscorp/ModuleInterface for this usage. 😄

That's what ModuleInterface is based on. But we get compiler arguments on the fly.

For an Apple framework the best way is to import it in a project and command click on the import statement, Xcode will load the interface.

Beware of this, `Bundle.module` represents the resource bundle from the caller site, so if you call from module A to instantiate a NIB in module B using that code, it...

I'm using this https://github.com/bq/mini-swift/blob/master/Scripts/update_docs.rb for my interface

But i'd like a more constant way of making this interfaces.

I've created https://github.com/minuscorp/ModuleInterface @MedAmineWinners for this purpose ^^