Conversation
- Preload associations (Passkeys, Profile) in UserDB repositories for auth and api services - Fix 'Found no credentials for user' error during WebAuthn BeginLogin - Add credentials: 'include' to frontend passkey login fetch calls - Ensure session cookies are correctly sent during login flow
- Update Preload calls in auth and api repositories to match gorm.G signature - Use 127.0.0.1 consistently in config and .env to avoid localhost resolution issues - Make API config controller dynamic based on loaded configuration
- Mount auth service under /auth and api service under /api - Configure Vite proxy to route /auth and /api to backend services - Switch frontend to use relative paths for service communication - Remove manual 'credentials: include' from fetch calls (now handled by same-origin proxy) - Update API config controller to return relative service paths
- Fix Preload calls with explicit builder functions to prevent panics - Confirm /auth and /api prefixes are working correctly in both services - Finalize relative paths in frontend for seamless Vite proxying - Verified entire flow with curl
- Add BackupEligible and BackupState to Passkey models and entities - Create migration to add backup flag columns to passkeys table - Update WebAuthn mapping to include persisted backup flags - Fix validation error 'Backup Eligible flag inconsistency detected during login validation'
GORM's CreateTable in migration 00002 already includes these columns because the Passkey model was updated before the table was created in the reset flow.
- Correct WebAuthn Credential mapping to use CredentialFlags - Fix BackupEligible and BackupState access in PasskeyManager - Update UserManager tests to match new pointer-based Create signature - Successfully verified with go build, go test and bun run build
…ment - Add DateOfBirth to Profile model and entities - Implement profileService.updateProfile in web service - Create Profile page with Ant Design form and validation - Add automatic redirection to /profile if user email is missing - Implement UpdateProfile usecase and handler in api service - Add unit tests for api UserManager.UpdateProfile - Fix all TypeScript and ESLint issues in web service
- Delegate user/profile management to api service - Implement AMQP Client (auth) and Server (api) for RPC and Events - Implement SAGA pattern for user creation with compensation logic - Update architecture documentation with Mermaid diagrams - Add RabbitMQ to Docker Compose and project config - Update unit tests and perform E2E verification
- Create Settings page with General and Auth Methods tabs - Add support for listing and unlinking OAuth providers in auth service - Add support for listing and deleting Passkeys in auth service - Implement account linking logic in OAuth callback - Update API config to return enabled providers - Protect management routes with JWTMiddleware in auth service - Fix various TypeScript and ESLint issues
…dded SQL migrations and AntD UI - Add Goose SQL migration for activities, activity_likes, and activity_comments tables - Implement GORM generic repository layer for social entities in api service - Implement usecase and HTTP controllers for liking/unliking activities and comment CRUD - Build React components (ActivityLikeButton, ActivityCommentSection, ActivityFeedCard) - Create AGENTS.md developer guide and update project constitution to v1.1.0
- Update Go module paths across auth, api, and dbm services to github.com/Linux-oiD/fitfeed/services/* - Replace relative fitfeed/* imports with full GitHub module URLs - Fix TypeScript any types in web components and pages to satisfy ESLint
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This pull request implements the social interaction features (Activity Likes & Comments) along with developer guidance and architectural governance.
Key Changes:
embed.FS.00003_add_activities_likes_and_comments.sqldefiningactivities,activity_likes, andactivity_commentstables.services/api):entityusecaserepocontroller).gorm.G[T](db)).POST/DELETE/api/v1/activities/:id/like) and comments CRUD (GET/POST/api/v1/activities/:id/comments,DELETE/api/v1/comments/:id).services/web):ActivityLikeButtonwith instant optimistic UI response (<200ms).ActivityCommentSectionwith comment form, whitespace validation, chronological thread rendering, and author-based deletion.ActivityFeedCardand updated the Home feed with interactive activity posting and summary badges..specify/memory/constitution.md) to v1.1.0.