Create multi module navigation ADR

Author: bilgehan.kalkan

architecture_decision_records/adr/0012-multi-module-navigation.md

@@ -0,0 +1,9 @@
+
+# Gradle Rules  
+
+ * Status: accepted  
+ * Date: 2021-06-24
+
+## Decision
+
+In the context of in app navigation between module facing concern of creating circular dependencies and causing longer build times we decided for creating navigation module and neglected using reflection to create fragment instances, to achieve in app navigation, accepting using argument classes as DTO, because using reflection breaks type safety.

architecture_decision_records/architecture_decision_records.md

@@ -14,5 +14,6 @@ This architecture decision log (ADL) is the collection of all ADRs created and m
 - [ADR-0009](adr/0009-gradle-rules.md) - Gradle file rules
 - [ADR-0010](adr/0010-dependency-rules.md) - Dependency configuration rules
 - [ADR-0011](adr/0011-resource-management.md) - Resource management
+- [ADR-0012](adr/0012-multi-module-navigation.md) - Multi module navigation
 
 For new ADRs, please use [template.md](https://github.com/Trendyol/android-guidelines/blob/master/architecture_decision_records/template.md) as basis. When this template was creating, we inspired from [MADR](https://adr.github.io/madr/).

module_guideline/module_guideline.md

@@ -17,5 +17,6 @@ There are total 5 levels on our concept:
 
 Lower level modules(eg `:common:common-models`) can be used by higher level modules(eg `:trendyol:authentication`) or in its level if not creating circular dependency.
 Level of a module is determined by its highest architectural level. For example `:trendyol:elite` has all 3 layers(ui, domain and data) and it's a level 1 but `:trendyol:filter-ui` has only ui layer but it's also a level 1 module.
+Level 2 and level 3 modules should be used across minimum 2 modules; otherwise do not separate as new module, use in higher level module.
 
 This separation helped us to create modularized by providing clear sight about dependency boundaries.