Replace location sharing with profile visibility

Replace the previous location-sharing privacy model with a profile-visibility feature. Renamed localization keys (en/es) and updated UI widget text. Added repository methods to get/update profile visibility using Data Connect, wired new GraphQL query (getStaffProfileVisibility) and mutation (UpdateStaffProfileVisibility), and added corresponding use cases (GetProfileVisibilityUseCase, UpdateProfileVisibilityUseCase). Updated BLoC, events, and state to use boolean isProfileVisible instead of PrivacySettingsEntity and removed old location-sharing usecases/entities. Also updated module DI and public exports accordingly; asset loading for legal docs kept with minor error logging.
This commit is contained in:
Achintha Isuru
2026-02-18 16:16:49 -05:00
parent c4d0d865d7
commit 6b43a570d6
17 changed files with 201 additions and 182 deletions

View File

@@ -214,3 +214,12 @@ mutation UpdateStaff(
mutation DeleteStaff($id: UUID!) @auth(level: USER) {
staff_delete(id: $id)
}
mutation UpdateStaffProfileVisibility($id: UUID!, $isProfileVisible: Boolean!) @auth(level: USER) {
staff_update(
id: $id
data: {
isProfileVisible: $isProfileVisible
}
)
}

View File

@@ -204,3 +204,10 @@ query filterStaff(
zipCode
}
}
query getStaffProfileVisibility($staffId: UUID!) @auth(level: USER) {
staff(id: $staffId) {
id
isProfileVisible
}
}