I've read the <Library Authors' Guidelines> and wo...
# getting-started
k
I've read the Library Authors' Guidelines and wondered about my current use case. I'm writing a multi-module application (a Gradle project using multiple source sets), with one module creating a library which is used by other modules as a dependency. The library is not used by anything outside this application. How much of the guidelines are worth following? I'm thinking that using Explicit API mode would be useful (to allow encapsulation) but most backward-compatibility advice such as avoiding data classes is not necessary because as soon as I change the library I recompile all the projects that use it. Am I on the right track?
j
As a side note: a multi-module application is a multi-project Gradle build, not a multi-source set Gradle project. This is usually quite different.
👍 1
Regarding your question, I wouldn't care too much about the guidelines in this case, they are mostly for published libraries
👍 1
plus1 1