Centralize Gitea domain workflows
This commit is contained in:
17
README.md
17
README.md
@@ -60,15 +60,16 @@ accepted as command-line arguments or environment variables.
|
||||
|
||||
## Architecture
|
||||
|
||||
The Rust core owns Gitea access, validation, presentation records, preferences,
|
||||
favorites, and Keychain-backed credentials. UniFFI generates the Swift bridge
|
||||
in `ios/Generated`. UIKit owns navigation, lists, text input, menus, scrolling,
|
||||
pull-to-refresh, appearance, and other platform behavior.
|
||||
`gotcha_gitea` owns Gitea access, authentication, validation, mutations, and
|
||||
relationships between Gitea objects. The CLI is a terminal presentation layer:
|
||||
it parses arguments and YAML, invokes shared client operations, and formats the
|
||||
results. `gotcha-app` owns application state, preferences, favorites,
|
||||
Keychain-backed credentials, and view-ready UniFFI records. UIKit owns native
|
||||
navigation, controls, layout, and other platform presentation behavior.
|
||||
|
||||
New API workflows should first be exercised and typed in the CLI, then exposed
|
||||
through the Rust core and presented with native UIKit controls. Future work
|
||||
includes write workflows and iOS integrations such as sharing, notifications,
|
||||
and background refresh.
|
||||
New Gitea workflows belong in `gotcha_gitea::Client` first, then receive CLI or
|
||||
app presentation as needed. Future work includes iOS integrations such as
|
||||
sharing, notifications, and background refresh.
|
||||
|
||||
## iOS app
|
||||
|
||||
|
||||
Reference in New Issue
Block a user