drop/desktop/main/components/ChatRoomGroup.vue
wdunn001 e8d3df032c
Some checks failed
Server CI / Lint (push) Failing after 9m53s
Server CI / Typecheck (push) Successful in 11m40s
desktop: native News, Friends, and Alerts pages; retire the browser-linkout Community tab
The News page was a hardcoded "under construction" stub, and the Friends/
Alerts header icons did nothing -- both replaced with real Vue pages/
widgets backed by the server's existing news/notifications/community APIs,
reached through a generic authenticated REST bridge (community_api.rs:
api_get/api_post/api_delete) and a websocket bridge for live chat/presence
(community_ws.rs, mirrors the reqwest_websocket pattern remote.rs already
uses for the auth-code exchange).

- News: GET /api/v1/client/news, rendered with micromark, with real
  loading/empty/error states.
- Alerts: GET/POST /api/v1/notifications/*, polled (not the notifications
  websocket -- see notifications.ts for why), unread badge + mark
  one/all read.
- Friends: full friends composable (list/requests/search/presence) plus a
  header dropdown and a /community/friends management page.
- Chat: /community/chat, rooms (server/global/title/DM) over the live
  community websocket with a REST history/read-state load on room switch.
- Achievements: per-game card on the library detail page and a per-user
  summary on the new read-only profile page (/community/profile/:username).
- The Community tab's "opens in your system browser" page is gone;
  /community is now a real in-app hub (activity feed + server list) linking
  into friends/chat.

Also fixes a real auth gap found by actually running the built client
against the live server: notifications/community routes are gated by
aclManager.getUserIdACL, which only accepts a session cookie or an opaque
Bearer APIToken -- never the client's own short-lived signed JWT
(generate_authorization_header). The client already had a bridge for this
(POST /api/v1/client/user/webtoken, JWT-authenticated, mints an opaque
token), but CLIENT_WEBTOKEN_ACLS never granted it the notifications/
community scopes, so the exchange succeeded and the minted token still got
403'd on every one of these routes. Extended that ACL list
(04.auth-init.ts) and switched community_api.rs/community_ws.rs to mint and
use that webtoken instead of the JWT for these specific calls.

Client version bumped to 0.4.2 (tauri.conf.json).
2026-08-03 19:42:50 -04:00

41 lines
1.3 KiB
Vue

<template>
<div v-if="rooms.length > 0" class="pt-3">
<p class="px-4 pb-1 text-[11px] uppercase tracking-wide text-zinc-500 font-semibold">
{{ label }}
</p>
<button
v-for="room in rooms"
:key="room.id"
@click="$emit('select', room.id)"
class="w-full flex items-center gap-x-2 px-4 py-2 text-left hover:bg-zinc-800/60 transition"
:class="active === room.id ? 'bg-zinc-800' : ''"
>
<CommunityAvatar v-if="room.kind === 'direct'" :url="room.otherUser?.avatarUrl ?? null" />
<HashtagIcon v-else class="h-5 w-5 text-zinc-500 shrink-0" />
<span class="text-sm text-zinc-200 truncate flex-1">{{ room.name }}</span>
<span
v-if="room.unreadCount > 0"
class="text-[11px] bg-blue-500 text-zinc-950 rounded-full min-w-[1.1rem] h-[1.1rem] px-1 text-center leading-[1.1rem] font-semibold"
>
{{ room.unreadCount }}
</span>
</button>
</div>
</template>
<script setup lang="ts">
import { HashtagIcon } from "@heroicons/vue/20/solid";
defineProps<{
label: string;
active?: string;
rooms: Array<{
id: string;
name: string;
kind: string;
unreadCount: number;
otherUser: { avatarUrl: string | null } | null;
}>;
}>();
defineEmits<{ select: [roomId: string] }>();
</script>