Package-level declarations

Types

Link copied to clipboard
class AuthRedirectHandler(authRepository: AuthRepository)

App-level consumer of the OAuth redirect deep link (GoogleAuthCallback). run is launched once at the root of App and lives as long as the app, so a redirect completes sign-in no matter which screen is visible. The normal flow returns while the login sheet is open — but a sign-in deep link can equally arrive with no sheet showing, even cold-starting the app, which is why the sheet can't own this collection.

Link copied to clipboard
interface AuthRepository
Link copied to clipboard
class AuthRepositoryImpl(authApi: AuthApi, sessionStorage: SessionStorage, scope: CoroutineScope, httpClients: List<HttpClient>) : AuthRepository
Link copied to clipboard
class BookmarkIdsStore(postsApi: PostsApi)

Holds the logged-in user's bookmarked post IDs so the (fully anonymous) feed endpoint never needs to know about auth — PostsRepositoryImpl stamps isBookmarked onto feed items by checking this set client-side. Only the first page is fetched for the ID set (a few thousand bookmarks would need real accumulation across pages; treated as an edge case to revisit, not a blocker).

Link copied to clipboard
interface PostsRepository
Link copied to clipboard
class PostsRepositoryImpl(postsApi: PostsApi, bookmarkIdsStore: BookmarkIdsStore, feedCache: FeedCache) : PostsRepository
Link copied to clipboard
Link copied to clipboard
class ProfileRepositoryImpl(authApi: AuthApi, session: StateFlow<Session?>, scope: CoroutineScope) : ProfileRepository
Link copied to clipboard
data class Session(val accessToken: String)
Link copied to clipboard

The catalogue of selectable topics (the Topic.All pseudo-topic is excluded - callers add it where a "show everything" option is wanted). Backed by TopicPreferencesStore's persisted catalogue (seeded with Topic.selectable on first launch) and reconciled against GET /v1/topics once per app open — a failed fetch is tolerated and just keeps the stored catalogue. Topics the server has that the catalogue doesn't surface in pendingNewTopics until acknowledgeNewTopics is called, so the UI can announce them once.

Link copied to clipboard
class TopicsRepositoryImpl(api: TopicsApi, store: TopicPreferencesStore, scope: CoroutineScope) : TopicsRepository
Link copied to clipboard

The phases an image upload passes through, reported via the onStage callbacks so the UI can show distinct feedback for each.

Link copied to clipboard

Deletes everything stored server-side for the current user in this app via DELETE /v1/me — server removes the bookmarks it holds and cascades to the auth server, which wipes the app-scoped profile data (uploaded images). See PRIVACY.md.

Link copied to clipboard