-
Notifications
You must be signed in to change notification settings - Fork 15
Show Car claims on claim card and history (RND-1677) #2930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
36 commits
Select commit
Hold shift + click to select a range
2f6d1d0
feat: add PartnerClaim type to GraphQL schema
hugokallstrom c46ab04
feat: add PartnerClaimFragment GraphQL fragment
hugokallstrom 07a2a6e
feat: add fromPartnerClaim factory methods for claim card UI state
hugokallstrom a2a1ff2
feat: merge partner claims into home screen claims pager
hugokallstrom 72b6ce9
feat: dispatch partner claim navigation from home screen
hugokallstrom 08d0b42
feat: merge partner claims into claim history
hugokallstrom f5210ee
refactor: extract shared claim detail composables to ui-claim-status
hugokallstrom 7740623
feat: add partner claim details module with simplified details screen
hugokallstrom d7cce70
feat: wire partner claim details into app navigation and DI
hugokallstrom ad5512e
fix: right-align arrow icon in partner claim email row
hugokallstrom c43dae0
fix: match email row styling to chat row pattern in claim details
hugokallstrom ad3d88c
fix: simplify email row to plain clickable card
hugokallstrom de0f652
fix: remove handler email from partner claim details screen
hugokallstrom 7b9621a
chore: update GraphQL schema from introspection
hugokallstrom 221c87c
chore: run ktlint formatting
hugokallstrom 94dd5cb
fix: handle empty claims list in home status cards and add lint baseline
hugokallstrom a69ea1e
docs: add design spec for unifying partner claim into regular claim d…
hugokallstrom 4cbe579
docs: add implementation plan for unifying partner claim detail
hugokallstrom 16e69fb
feat: add isPartnerClaim flag to claim detail destination and wire th…
hugokallstrom 9759d7d
feat: add partner claim query support to GetClaimDetailUiStateUseCase
hugokallstrom 4e19eea
fix: hide uploaded files header when no submitted content or files
hugokallstrom 2695345
refactor: unify claim detail navigation — remove partner-specific cal…
hugokallstrom 75a1517
refactor: delete feature-partner-claim-details module and all references
hugokallstrom dffcca6
chore: remove accidentally staged worktree
hugokallstrom 6bc0a31
chore: run ktlint formatting
hugokallstrom 042cabe
fix: use kotlin.time.Clock instead of kotlinx.datetime.Clock
hugokallstrom 474926b
fix: show submitted date instead of exposure name on partner claim cards
hugokallstrom ed5daf4
chore: remove design spec and implementation plan docs
hugokallstrom 2d90eb6
refactor: move shared claim detail composables back to feature-claim-…
hugokallstrom 3089a81
chore: restore original function ordering in ClaimDetailsDestination …
hugokallstrom 0847a4b
fix: address review on partner claim flow + iOS parity
hugokallstrom cea78ef
chore: download strings
hugokallstrom f486b9e
refactor: simplify partner-claim fallback in GetClaimDetailUiStateUse…
hugokallstrom a44fe35
chore: add isPartnerClaim flag to ClaimStatusCardUiState
hugokallstrom 318ca9a
Revert "chore: add isPartnerClaim flag to ClaimStatusCardUiState"
hugokallstrom 28892c2
Merge remote-tracking branch 'origin/develop' into feat/show-car-claims
hugokallstrom File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
25 changes: 25 additions & 0 deletions
25
...in/graphql/com/hedvig/android/apollo/octopus/graphql/FragmentPartnerClaimFragment.graphql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| fragment PartnerClaimFragment on PartnerClaim { | ||
| id | ||
| externalId | ||
| exposureDisplayName | ||
| status | ||
| submittedAt | ||
| payoutAmount { | ||
| ...MoneyFragment | ||
| } | ||
| associatedTypeOfContract | ||
| claimType | ||
| handlerEmail | ||
| displayItems { | ||
| displayTitle | ||
| displayValue | ||
| } | ||
| productVariant { | ||
| typeOfContract | ||
| displayName | ||
| documents { | ||
| type | ||
| url | ||
| } | ||
| } | ||
| } |
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
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
5 changes: 5 additions & 0 deletions
5
app/feature/feature-claim-details/src/main/graphql/QueryPartnerClaim.graphql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| query PartnerClaimDetail($claimId: ID!) { | ||
| partnerClaim(id: $claimId) { | ||
| ...PartnerClaimFragment | ||
| } | ||
| } |
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember there being some problems with having the outcome here from the BE, right? So we can't really have status "Paid" and payout can only be mentioned in the details?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no "10000 kr", "Paid" pill on the card, I mean
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct, we dont get outcome from EIR.