Skip to content

Ra/refactor/presentation module boundary - #5

Merged
ramyassaf merged 2 commits into
devfrom
ra/refactor/presentation-module-boundary
Jun 8, 2026
Merged

Ra/refactor/presentation module boundary#5
ramyassaf merged 2 commits into
devfrom
ra/refactor/presentation-module-boundary

Conversation

@ramyassaf

Copy link
Copy Markdown
Owner

No description provided.

Ramy ASSAF added 2 commits June 5, 2026 09:39
Move Compose UI, navigation, ViewModels, UI state, theme, and presentation mapping into a dedicated presentation module.

Keep the app module focused on Android startup and composition wiring while preserving existing runtime behavior.
Isolate the Clean Architecture module dependency-direction check out of the
root build script into a dedicated build-logic convention plugin
(com.compose.chi.module-architecture). This keeps the root build declarative
and turns the allowed module graph into a single, reusable contract that the
build proves on every local and CI run via the verifyModuleArchitecture task
(wired into `check` and run as its own CI step).

Move enforcement of inter-module dependency direction from source-level
Konsist rules to a structural, build-level check. The module graph is a build
concern: Gradle's project/dependency APIs prove it completely and fail fast,
even on arrows the compiler accepts, such as one Android library depending on
another. Konsist is refocused on the code-shape rules it expresses best
(domain purity, layer placement, composition-root imports).
Align module docs with the presentation module split
@ramyassaf
ramyassaf merged commit eb9efda into dev Jun 8, 2026
1 check passed
@ramyassaf
ramyassaf deleted the ra/refactor/presentation-module-boundary branch June 8, 2026 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant