Skip to content

Feature/co owners#2873

Open
StylianosGakis wants to merge 26 commits intodevelopfrom
feature/co-owners
Open

Feature/co owners#2873
StylianosGakis wants to merge 26 commits intodevelopfrom
feature/co-owners

Conversation

@StylianosGakis
Copy link
Member

Co-owners WIP as schema is not yet finalized

Introduces a shared data-coinsured module containing CoInsuredFlowType,
a sealed enum distinguishing co-insured vs co-owner flows. This allows
downstream modules to navigate to the right type of edit flow
Fetches the two new backend fields across all queries that already fetch
coInsured/supportsCoInsured, so each module has the data it needs to
display and manage co-owners.
Extends InsuranceContract and InsuranceAgreement with coOwners list and
supportsEditCoOwners flag, mapped from the newly fetched GraphQL fields.
The flag reuses the same edit-coinsured feature flag gate.
GetNeedsCoInsuredInfoRemindersUseCase now checks coOwners in addition to
coInsured for missing info. MemberReminder.CoInsuredInfo carries a
CoInsuredFlowType so reminder card navigation can route to the correct
edit flow.
…ontracts

Replaces isCoOwner: Boolean with CoInsuredFlowType in navigation
destinations, ViewModel, Presenter, and triage. The triage screen now
also surfaces co-owner contracts (supportsCoOwners) alongside co-insured
ones, allowing the same edit flow to handle both types by switching on
the flow type.
YourInfoTab renders co-owners in a separate section below co-insured.
EditInsuranceBottomSheet exposes a dedicated edit co-owners option when
supportsEditCoOwners is true, navigating to the edit flow with
CoInsuredFlowType.CoOwners.
GetQuickLinksUseCase now generates QuickLinkCoOwnerAddInfo and
QuickLinkCoOwnerAddOrRemove destinations for contracts that support
co-owners, mirroring the existing co-insured quick link logic.
HedvigNavHost connects startEditCoOwners and startEditCoOwnersAddMissingInfo
to the edit flow with CoInsuredFlowType.CoOwners. Home, insurance list,
terminated contracts, and profile screens thread the new lambdas through
to the top-level nav host.
# Conflicts:
#	app/apollo/apollo-octopus-public/src/commonMain/graphql/com/hedvig/android/apollo/octopus/schema.graphqls
@StylianosGakis StylianosGakis marked this pull request as ready for review March 11, 2026 13:30
@StylianosGakis StylianosGakis requested a review from a team as a code owner March 11, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant