Channels
#android-architecture
Title
# android-architecture
g
ghedeon
06/20/2018, 5:47 PMcall me "courageous" but I stopped using packages for my apps). I just have a root "app" package and the actual application ID is being replaced by gradle. Why have nested folders
com.smoothie.gyroscooterg
gildor
06/21/2018, 5:13 AMKotlin style guide actually recomments to emit empty package dirs and this what people from JB and Kotlin Team do, also they do not use standard maven layout:
src/(main|test)/(kotlin|java)/src/test/Found it
In pure Kotlin projects, the recommended directory structure is to follow the package structure with the common root package omitted (e.g. if all the code in the project is in the “org.example.kotlin” package and its subpackages, files with the “org.example.kotlin” package should be placed directly under the source root, and files in “org.example.kotlin.foo.bar” should be in the “foo/bar” subdirectory of the source root).https://kotlinlang.org/docs/reference/coding-conventions.html
g
ghedeon
06/21/2018, 9:06 AMWith all due respect to kotlin, I believe on android the project layout is dictated by the gradle plugin. And even tho you can redefine source sets in gradle, I doubt it's worth the trouble to mess with non-orthodox paths, considering build variants and flavors... But at least flat packages are easy and it's for free, with the help of the built-in
applicationIdapplicationIdg
gildor
06/21/2018, 9:08 AMdictated by the gradle pluginnot dictated, but gradle plugin has default layout and not only on Android, same with Java projects
why not just omit empty dirs, I don’t understand why do you need applicationId for that?
applicationId and app package are not related, it’s just common practice to have the same appId and basic package
also there is no requirement to have package equal to dir structure, it’s also just a common practice because of java
considering build variants and flavorsexactly, default layout is created to allow easily add some code to another source set and this source set can be used by particular build type or flavor, but if you don’t use it, I don’t think that there is any problems with it
a
arekolek
06/21/2018, 9:18 AMI stopped using packages for my appsdo you use modules though? or is it all in the same module in the same package
g
gildor
06/21/2018, 9:24 AMI don’t see any problem with packages, it’s just how you organize code. And “nested folders `com.smoothie.gyroscooter`” is not a problem of packages and separation of code, just a base package
g
ghedeon
06/21/2018, 9:28 AM@arekolek maybe I worded that poorly, assuming your default package is “org.example.kotlin.foo.bar” I reduce it to "app" or just nothing and set
applicationIdsrc/main/java/Foo.ktg
gildor
06/21/2018, 9:29 AMapplicationId is not related on your default package
and source path can be src/main/java/Foo.kt even if Foo package is com.smoothie.gyroscooter
all those 3 things are not related
g
ghedeon
06/21/2018, 9:31 AMthat's right, but than you have to be more specific with the question. In my understanding, the question was about actual folders structure and by default, AS generates nested folders that reflect the package
g
gildor
06/21/2018, 9:32 AMyou can just delete them (empty dirs with default package) and no need even change build config
g
ghedeon
06/21/2018, 9:33 AMthat's what I do
not for the library, tho
because we're back to no
applicationIdso, it's not really "completely unrelated"
in absence of
applicationIdpackage org.example.kotlin.foo.bar>dictated by the gradle plugin
not dictated, but gradle plugin has default layouttautology
@arekolek as for the modules, @gildor rightfully mentioned that it's up to you, how you want to organize your code. I've seen people even having different modules for every app layer:
datadomainuig
gildor
06/21/2018, 10:17 AMexplicitly specify the desired package for your files (ex:Yes, it’s true, you have to specify package. But for library you can just use any package, like)package org.example.kotlin.foo.bar
myliborg.example.mylib6 Views