You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(Mountain): standardize naming conventions and directory structure
- Rename `AppState` to `ApplicationState` across Mountain component to align with Land's architectural documentation
- Refactor `handlers` directory to `Handler` following project's PascalCase convention for core modules
- Update `runtime` references to `RunTime` matching updated terminology in README.md
- Normalize gRPC-related abbreviations (e.g. `VineGRPC` -> `VinegRPC`) per style guidelines
- Reorganize environment provider implementations to match `Common` trait definitions
- Adjust module declarations to use consistent naming for Effect-TS alignment
This restructuring improves codebase consistency with Land's final architecture while maintaining all existing functionality for Cocoon integration and gRPC communication.
|**Implementation of Contracts**| Faithfully implement the abstract service `trait`s defined in the `Common` crate, providing the concrete logic for the application's architecture. |`environment/*` providers |
66
-
|**Separation of Concerns**| Isolate business logic in `handlers` modules, keeping the `environment` provider implementations clean and focused on delegation. |`environment/*`, `handlers/*`|
67
-
|**Declarative Logic**| Express all operations as `ActionEffect`s, which are executed by the `AppRuntime`. This makes logic composable, testable, and robust. |`runtime/*`, `track/*`, `Common::effect`|
68
-
|**Centralized State**| Maintain a single, thread-safe `AppState` struct managed by Tauri to ensure data consistency across the entire application.|`app_state/*`|
66
+
|**Separation of Concerns**| Isolate business logic in `Handler` modules, keeping the `environment` provider implementations clean and focused on delegation. |`environment/*`, `Handler/*`|
67
+
|**Declarative Logic**| Express all operations as `ActionEffect`s, which are executed by the `ApplicationRunTime`. This makes logic composable, testable, and robust. |`RunTime/*`, `track/*`, `Common::effect`|
68
+
|**Centralized State**| Maintain a single, thread-safe `ApplicationState` struct managed by Tauri to ensure data consistency across the entire application. |`app_state/*`|
69
69
|**Secure & Performant IPC**| Utilize gRPC for all communication with the `Cocoon` sidecar, ensuring a well-defined and high-performance API boundary. |`vine/*`|
70
-
|**UI-Backend Decoupling**| Interact with the `Wind` frontend exclusively through asynchronous Tauri commands and events, ensuring the backend is UI-agnostic. |`main.rs` (invoke handler), `handlers/*` (emitters) |
70
+
|**UI-Backend Decoupling**| Interact with the `Wind` frontend exclusively through asynchronous Tauri commands and events, ensuring the backend is UI-agnostic. |`main.rs` (invoke handler), `Handler/*` (emitters) |
71
71
72
72
---
73
73
@@ -76,8 +76,8 @@ frontend and the `Cocoon` extension host.
76
76
To understand how `Mountain`'s internal components are structured and how they
77
77
implement the application's core logic, please refer to the detailed technical
78
78
breakdown in [`docs/Deep Dive.md`](docs/Deep%20Dive.md). This document explains
79
-
the roles of the `AppRuntime`, `AppState`, `handlers`, `environment`, and the
80
-
`Vine` gRPC layer.
79
+
the roles of the `ApplicationRunTime`, `ApplicationState`, `Handler`, `environment`,
0 commit comments