Refactor the title section to use raw icon components instead of Button components.
- Removed the surrounding <Flex> wrapper for the name and action.
- Removed the "取消关注" (Unfollow) and "关注" (Follow) text labels.
- Replaced Button components with direct StarFilled and StarOutlined icons
to reduce visual clutter and align with the icon-only design.
- Add minWidth: 180 to the main flex container to prevent excessive shrinking.
- Change the search input container width from fixed minWidth: 400 to dynamic width: '100%' with a new minWidth: 200.
This ensures better responsiveness on smaller screens while maintaining usability.
Introduce a follow/unfollow feature for clubs in the ClubSummary component.
Users can now toggle their subscription status to a specific club, with
the state persisted locally using zustand.
Changes include:
- Added 'Follow' and 'Unfollow' buttons with corresponding star icons (StarOutlined/StarFilled).
- Updated ClubStore to manage a simplified list of clubs (id and name only).
- Refactored Data type in ClubSearchTable to use Pick<ClubInfo, 'id' | 'name'>.
- Fixed club name in GameSelector clubList to '东华乒乓球俱乐部'.
- Excluded follow buttons for club ID '47' (Donghua).
The implementation ensures a consistent UI state across the application
and persists user preferences.
- Remove web-push and related sub-dependencies (asn1.js, http_ece, etc.) from package.json and bun.lock
- Update AppBar z-index to 8 for proper layering
- Enhance GameTable component:
- Add Skeleton loading states for event names
- Introduce EventName component with Link to event detail pages
- Fix column widths and add row-span logic for event grouping
- Enable horizontal scrolling for better mobile view
- Add /api/match-summary/:matchId endpoint for frontend event name fetching
- Rename getEventInfo to getMatchSummary in KaiqiuService for consistency
Removes the console.debug statement for 'clubId' from the method. This cleanup is performed to eliminate unnecessary debug output in production code and improve log clarity.
- Extract club information (clubId, clubName) from event page in `getEventInfo`.
- Update `getMatchDetail` to return both `detail` and `summary`.
- Introduce `MatchSummary` interface in `src/types/index.ts`.
- Update `EventPage` to display the club name and link to the club page.
- Adjust `EventSubscribeService` and loaders to handle the new return structure.
- Clean up test files and mock data loading logic.
- Capitalize 'Event' in debug logs for consistency
- Fix syntax error in EventWatchSchedule debug message (removed trailing backtick)
- Upgrade subscription error logging from debug to error level for better visibility
- Standardize event URL format in match detail logs
These changes improve logging accuracy and ensure critical subscription errors are not missed.
- Replace Promise.all concurrency with sequential for...of loop when fetching event info and match details
- Add console.debug logs to track event processing status and URL retrieval
- Improves visibility into the event fetching flow for easier debugging
- Ensures events are processed one by one before being categorized
Add console.debug logs at the beginning and end of the getUidScore
function in uidScoreStore to track execution flow and performance.
This aids in debugging when the function is called with large lists
of uids.
- Log start entry with uid count
- Log end entry with uid count
- Add CascaderProvinceCity component to ClubSearchTable for selecting province/city.
- Update KaiqiuService.findClub to accept and append province/city parameters to the query URL.
- Update server-side API handler to extract province/city from query parameters.
- Improve date parsing logic in event processing to handle invalid start dates gracefully.
- Refactor uidScoreStore to use a loop instead of map for better performance/clarity.
- Add debug logging for profile caching in xcxApi.
The search functionality now supports filtering clubs by administrative division, providing users with more precise search results.
- Replace null return with Skeleton.Input when binding status is undefined
- Wrap bound account display in a Button with Space layout
- Import Skeleton and Space components from antd
This enhances the user experience by providing a loading skeleton
and making the bound account view more interactive.
Wrap the verifyLogtoToken promise with a catch block to prevent
unhandled promise rejections. When token verification fails,
return an empty payload instead of throwing an error, ensuring
the application continues to run without crashing.
- Added .catch(() => ({ payload: {} })) to the token verification logic
- Prevents downstream errors when the token is invalid or missing
- Replace the static `cacheKey` with `refreshDeps: [headers]` in the
query configuration.
- This ensures the cached data is automatically refreshed when the
headers dependency changes, rather than relying on a static cache
identifier.
- Remove Redis-based caching logic from uidScoreStore and xcxApi.
- Add force refresh support to uidScoreRequest in GroupingPrediction component.
- Update server API /api/user/nowScores to accept force parameter.
- Always show refresh button in GroupingPrediction regardless of data state.
- Change default sort type in FavPlayersPage to SCORE_DOWN.
- Clean up unused imports from server.ts.
This change ensures user scores are always up-to-date by bypassing cache
when needed, preventing issues with stale data during manual sync operations.
- Move `parseEventInfo` and `fetchEventContentHTML` logic into `KaiqiuService`.
- Implement differentiated caching strategies:
- For finished matches: Cache indefinitely (no TTL) to stop unnecessary HTTP requests since the result is final.
- For ongoing matches: Retain the 5-minute TTL to fetch live updates.
- Remove unused utility functions from `server.ts`.
- Update type imports to include `EventDetail` and `Player`.
This change reduces server load by avoiding repeated requests for matches with confirmed results, while ensuring live games remain up-to-date.
Replace the previous base image 'oven/bun:latest' with 'dhi.io/bun:1-debian13-dev'.
This updates the underlying OS to Debian 13 and pins the Bun version for better consistency.
Replace the nodeSchedule.Range object with a literal array for the
hour parameter in the event watch schedule. This makes the scheduled
hours (7 to 22) more explicit and easier to read at a glance, while
maintaining the exact same execution logic.
The scheduled job for watching events was previously set to run until
hour 23. This changes the `nodeSchedule.Range` end hour from 23 to 22
to ensure the job stops execution correctly before the end of the day.
This is a bug fix to align the actual execution window with the intended
operating hours.
No breaking changes.
Introduce a bottom drawer in the notification permission control
component to provide a step-by-step guide for users (specifically
on iOS/Safari) to enable push notifications when the browser does
not support direct requests.
Key changes:
- Added a 'Drawer' component with 'placement="bottom"' to display
instructions for adding the site to the home screen.
- Updated the permission control panel to use the same bottom
placement for consistency.
- Refactored the notification control to toggle the drawer state
upon interaction.
This improves the user experience by explicitly showing how to
enable features that are restricted in PWA-like environments.
Introduce Redis caching logic to `getClubInfo` and `getMatchDetail` methods in `KaiqiuService` to improve performance and reduce network requests.
- Added optional `force` parameter to bypass cache when needed.
- Implemented cache fallback for connection timeouts.
- Updated cache expiration times (e.g., 24h for club info, 5m for match details).
- Propagated the `force` parameter from `EventSubscribeService` to ensure data freshness.
Update the `info` array generation logic to concatenate the `see` and `nums` values into a single string separated by a space, instead of keeping them as separate array elements.
This change standardizes the format of the information display for match events.
- Extract 'nums' (号码) and 'see' (查看次数) from event page content.
- Include extracted data in the `IEventInfo` structure for display.
- Implement Redis caching for event details (key: `my-kaiqiuwang:event-info:${eventId}`).
- Cache strategy: Store result for 60 seconds, or refresh if cached data shows timeout errors or force flag is set.
- Reduces redundant external requests and improves response reliability.
Added volume mappings for /etc/localtime and /etc/timezone to ensure
the container uses the host's time and timezone settings.
This prevents time discrepancies in logs and scheduled tasks without
requiring manual timezone configuration inside the image.
- Introduce Redis caching for event lists to reduce redundant fetches and handle timeouts gracefully. Added a `force` query parameter to bypass cache when needed.
- Added a check in `EventWatchSchedule` to skip processing if player list is empty, preventing errors from rate-limited or failed requests.
- Updated the `listClubEvents` signature to accept the new `force` parameter and modified API endpoints to propagate this flag.
- Import and extend 'dayjs' with 'utc' and 'timezone' plugins.
- Update logging in 'watchEvents' and 'start' methods to explicitly format
dates in 'Asia/Tokyo' timezone instead of default system time.
- This ensures consistent timestamp representation across different deployment
environments regardless of the local server timezone.
- Import 'dayjs' to format timestamps for better readability.
- Store the scheduled job instance in a private field to access next execution time.
- Update the 'start' method to log the job name and the precise next run time.
- Update 'watchEvents' method with a debug log for the next invocation.
This improves observability by showing exactly when the scheduled task is expected to run next, rather than just the schedule definition.
Replace the string '7-23' with new nodeSchedule.Range(7, 23) for the hour configuration.
This change aligns the schedule definition with the explicit Range object type,
potentially improving type safety or ensuring compatibility with the underlying node-schedule library behavior.
The event watch schedule was previously running every 5 minutes all day.
Added 'hour: 7-23' configuration to restrict the task execution to
business hours, preventing unnecessary load during off-peak times.
- Update useFirebaseNotificationProcessor to handle notification clicks by opening the URL from data.url.
- Implement notificationclick event handler in sw.ts to redirect users when a notification is clicked.
- Simplify the registration success notification in index.tsx by removing the unnecessary JSON body argument.
- Ensure seamless navigation when users interact with push notifications by passing the URL through the notification payload.
- Introduce PermissionControlPanel in UserCenter for managing notification permissions.
- Update Service Worker (sw.ts) to handle background push notifications via Firebase Cloud Messaging.
- Implement EventSubscribeService logic to fetch active events, filter expired ones, and clean up subscriptions.
- Refactor KaiqiuService and parsing utilities to include eventId in event details.
- Remove deprecated ScheduleService and inline sendNotification logic.
- Update utility functions to support new types and notification checks.
- Add VAPI public key configuration and update Firebase exports.
Refactor the application to implement native browser push notifications and remove unnecessary Redis caching for performance optimization.
Key changes:
- Introduce a dedicated server topic 'SERVER_PUSH' to handle push notification messages via WebSocket.
- Implement a Service Worker (sw.ts) to capture push events and display system-level notifications, replacing the previous Ant Design toast usage for server messages.
- Add a "Notification Permission" button in the User Center to allow users to request push notification rights.
- Remove Redis caching logic from KaiqiuService (event lists, match details, and member details) to ensure real-time data accuracy, as the cache was causing latency in updates.
- Clean up WebSocket service subscription logic to focus on user-specific events.
This shift from UI-only notifications to system push notifications improves visibility for critical server events (like match updates) even when the user is not on the active tab. Additionally, removing the cache simplifies the codebase and ensures the latest match data is always fetched.
Previously, the refresh button was hidden whenever the cached uidScore size
was greater than 0, or when the cached data was empty. This logic prevented
the button from appearing even after a data request successfully returned
data in uidScoreRequest.
The updated logic now checks both the cached uidScore and the request data.
If either contains data, the button is shown, ensuring users can refresh
scores regardless of the caching state.
- Add `.catch(() => null)` in `ClubSummary.tsx` to gracefully handle failed API requests and prevent UI crashes.
- Return `null` from `ClubSummary` when the club data is `null` to skip rendering during errors.
- Extract `getMatchInfo` logic into a new static method `getMatchDetail` within `KaiqiuService` for better separation of concerns.
- Update `getClubLocation` and `getEventInfo` to accept an optional `force` parameter, allowing cache bypass when network errors (like '连接超时') occur.
- Remove the old `getMatchInfo` utility function from `server.ts` and update the `/api/match` route to use `KaiqiuService.getMatchDetail`.
- Refactor `WebSocketService` and `common.ts` to use a unified topic system instead of custom prefixes.
- Replace manual topic string concatenation with `getEventSubKey` and defined `WsServerSendTopics` types.
- Update client-side components (`EventCard`, `GroupingPrediction`) to support real-time event subscriptions and notifications.
- Move `useAuthSocket` and `WebScoketContext` initialization into `AppBarLayout` to ensure WebSocket state is available globally.
- Add error handling to WebSocket message processing in the Bun server.
- Implement a manual "Refresh Current Scores" button for `GroupingPrediction` to fetch fresh `nowScore` data.
- Update `HydrateFallback` UI to display a loading message instead of a refresh button during long load times.
- Add Service Worker (`sw.js`) build route to the Bun server configuration.
- Added `UserLocation` model to `prisma/schema.prisma` to store user location data including coordinates (point geometry), name, avatar, and bindings to Logto and Kaiqiu users.
- Created new API endpoints under `/api/account/location` to handle location operations:
- `POST`: Create a new location record for a user.
- `GET`: Retrieve nearby locations based on latitude and longitude.
- `PUT`: Update an existing location record, including coordinate updates via spatial index.
- `DELETE`: Remove a specific location record.
- Integrated the custom spatial operations from `xprisma` DAO to support geospatial queries and updates.
- Updated dependencies to include `@mui/icons-material` (and its peer dependencies like `prop-types` and `react-transition-group` which are implicitly required by the new icon components).
- Implemented `verifyLogtoToken` logic to secure the new endpoints and associate locations with authenticated users.
No breaking changes in API contracts; new endpoints are additive.
- Update HydrateFallback to show a refresh button after 10 seconds of loading
- Improve UserCenter avatar by using username/name as fallback when image is missing
- Add /dev route pointing to HydrateFallback component
This commit introduces a new `ChangeBackground` component into the User Center page.
The component is now rendered before the main content to dynamically update the
background based on the user's picture URL.
- Added import for `ChangeBackground` component.
- Integrated `ChangeBackground` with the user's picture URL (falling back to empty string if unavailable).
- No breaking changes or migration required.
Refactor the Dockerfile to separate dependency installation and type
generation from the runtime environment.
Changes:
- Moved `bun prisma generate` to the build phase to ensure type definitions
are created during image build rather than at runtime.
- Updated the ENTRYPOINT to run `bun prisma migrate deploy` before starting
the application. This ensures database migrations are applied automatically
upon container startup, supporting production deployments with incremental
schema changes.
- Added missing newline at the end of the file for compliance.
This change ensures that the application handles schema updates safely in
production without requiring a separate migration step outside the container.
- Modified `BindKaiqiuAccount` to wrap the UID text in a clickable `Flex` component.
- Added an `ExportOutlined` icon to indicate the actionable link.
- Implemented navigation to `/profile/{uid}` when the UID section is clicked, utilizing the `useNavigate` hook.
- Imported the new icon and navigation hook to support this interaction.
- Add `UserBind` model to Prisma schema for linking Logto and Kaiqiu user IDs.
- Implement `/api/account/bind` endpoint (GET/PUT) to handle Kaiqiu account binding and retrieval.
- Refactor `KaiqiuService` to include a `login` method that performs browser automation-like login on kaiqiuwang.cc using `cheerio` and `fetch`.
- Update `UserCenter` page to include a new `BindKaiqiuAccount` component.
- Restructure `WebSocketService`:
- Change from a simple global connection map to a per-user client tracking system (`#userClients`).
- Update topic naming conventions (e.g., `ONLINE_MEMBER_CHANGE` -> `MEMBER_CHANGE`).
- Add client-side broadcast capabilities for user-specific events like `MY_CLIENT_ONLINE`.
- Add support for dynamic subscription handling (SUB/UNSUB) via WebSocket messages.
- Update `verifyLogtoToken` to accept either `Headers` or a raw token string for flexibility in WebSocket auth.
- Minor fixes: typo corrections in `WSTopic` enum and commented out debug logs.
BREAKING CHANGE: WebSocket payload structure has changed.
The `ws.data` property now contains a `WsPaylaod` object with a `user` field (previously it was a JSON string of the JWT payload).
The `WSTopic` names have been updated (e.g., `ONLINE_MEMBER_CHANGE` is now `MEMBER_CHANGE`), requiring updates to any client code subscribing to these topics.
Introduces WebSocket connectivity for live data updates and a new subscription model for events.
Key changes:
- Integrated WebSocketService to handle open, message, and close events via the /ws endpoint.
- Added EventSubscribeService APIs to manage user subscriptions to specific events (matchId) via REST endpoints (`/api/subscribe-event` and `/api/subscribe-event/:matchId`).
- Implemented custom message protocol (JSON format) for WebSocket communication with defined topics (ONLINE_MEMBER_CHANGE, etc.).
- Updated database schema to include the `EventSubs` model for storing subscriptions.
- Refactored Dockerfile to use `bun prisma db push` for database migrations on startup.
- UI Updates:
- Replaced the Rate component in FavButton with Star icons for better UX.
- Adjusted layout of FavButton to be absolute positioned.
- Added debounce to ClubSummary data fetching.
- Removed unused `isMobile` import from ClubSummary.
- Utilities: Added helper functions `toCustomMessage` and `fromCustomMessage` for parsing WebSocket messages.
- Remove `getGitHash` function from `src/utils/server.ts` as it relied on `.git` directory presence which is not available in production builds.
- Remove the `/api/app-version` endpoint from `src/index.tsx` since fetching version via API is no longer needed.
- Update `src/hooks/useAppVersion.ts` to derive the version directly from the `src` attribute of a script tag in the HTML head.
- This change improves performance by avoiding an extra API request and ensures version accuracy across all deployment environments without requiring Git metadata.
