Conversation
…nvite` to `family` API - Refactor management context queries to use family API - Updated all instances of `api.invite.getManagementContext` to `api.family.getManagementContext` across various components and pages. - Introduced a new `familyRouter` to handle family-related API calls. - Removed the old invite management context logic from the invite router. - Added tests for the new family identity management functionality, ensuring proper handling of branding configurations and permissions.
…pdate MemberCard layout
refactor MemberStatusBadge import and add MemberRoleBadge component
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
This pull request focuses on improving consistency in API usage, enhancing the member invitation flow, and refining the display and filtering of family members across several pages. The most important changes are grouped as follows:
API Consistency and Refactoring
api.invite.getManagementContextwithapi.family.getManagementContextacross the codebase for a more accurate and consistent API reference. This change touches many pages, including gallery, member profile, members list, notifications, feed, post, profile, account settings, domain settings, family settings, and integrations settings. [1] src/app/(app)/member/[slug]/page.tsxL120-R120, [2] [3] [4] [5] src/app/(app)/post/[postId]/page.tsxL266-R266, [6] [7] [8] [9] [10]api.invite.updateFamilyIdentityandtrpcUtils.invite.getManagementContext.invalidate()to theirapi.familyequivalents in family settings. [1] [2]Member Invitation Flow Improvements
Member List and Profile Display Updates
addedByNameand instead display a dynamic label based on the member’s status (e.g., "Joined", "Invited", "Added") with relative time, and updated the search input to only filter by member name. [1] [2] [3] [4] [5]addedByName: "Family organizer"label from member and profile displays for a more accurate and streamlined UI. (src/app/(app)/member/[slug]/page.tsxL153, src/app/(app)/profile/page.tsxL134)UI and Component Updates
Badgecomponent import in invites settings, likely for new UI elements.Data Structure Updates
isClaimInviteandclaimMemberfields, preparing for more detailed invite management and display.These changes collectively improve maintainability, invite management flexibility, and the clarity of member information in the UI.
Screencast/Screenshot
screen-capture.84.webm