Is it feasible? If not, do you know any other way ...
# dokka
j
Is it feasible? If not, do you know any other way of doing that even by the compiler, IntelliJ or any other tool?
c
Do you mean listing the signatures of all classes/methods/properties/etc for an entire project in one file?
j
Yes
I’m thinking maybe I can use the reflection API in one test to achieve that (generate the list of signatures when the test is run)
c
I’ve built Kodiak as a wrapper around Dokka which should be able to help you do this. I built it for Orchid, but it’s a standalone tool https://github.com/copper-leaf/kodiak/tree/master/dokka
j
Thanks!
s
You could also take advantage over the dokka -plugin apis and create a plugin that does this for you. We are going to publish more information about this in the future!
j
@Sebastian Sellmair [JB] Do I have to switch to the development version (0.11) for this? If so, do I have to do a lot of changes to migrate from 0.10 to 0.11?
s
Yes, you would need to switch to 1.4.0-M3-dev-* or 0.11.0-dev-* releases for this! Regarding changes: Of course this depends on how much you configured dokka. We tried to keep many things compatible, but on the other hand we tried to improve the configuration site (and we are still not 100% happy with the current state)
Feel free to send me a direct message if you encounter issues or frustrations when upgrading 👍
j
Good I’ll give it a quick try. And if I find problems I will try Kodiak which seems very promising. Thank you both.