Nested Modules / Protocols

[Adzz]

Open Q on how to handle them. In theory it's on the user to generate a livebook for a nested module manually, but it gets a bit murky when we think of protocol implementations. Should the user really have to crawl through all of them?

I suppose that wouldn't be too bad if you first got all modules and then generated them but it might be hard to know which are your modules and which are like elixir core modules?

We would have to find all protocols in the app, then see if our module implemented any of them, then construct the module name and generate the docs for that module. I plan on trying this at some point, but for now I put a note in the README about it.