-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Fix new individual invoice after one is paid as a business #54138
Changes from all commits
bac1302
59d79fa
0afdca3
3054897
401f5de
3d11b6c
03c9bf9
0c6e50d
a2bbb54
410868e
57ba052
e6d5a92
2ada6b8
3e4e033
4516d8f
17d298a
5fefb6c
b62ad1b
7275ccf
68cabf2
b89a319
55572c3
3e56f47
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -62,6 +62,7 @@ type WhitelistedReport = OnyxCommon.OnyxValueWithOfflineFeedback< | |
}; | ||
// eslint-disable-next-line @typescript-eslint/naming-convention | ||
private_isArchived: unknown; | ||
welcomeMessage: unknown; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this comment is strange. The whole thing is pretty confusing. It's just listing all the fields in the report and asserting that they're in the report type. I don't find any value in that because it's totally circular. I found the related issue, and the goal there is to move client only keys out of the report type. So now I understand the purpose. It also doesn't really make sense to limit that to the OpenApp call, I think OpenReport is also a valid way to tell which keys come from the server. I checked the response and I see that welcomeMessage is returned but state is not, so I'll remove state. Thanks for pointing this out. |
||
}, | ||
PolicyReportField['fieldID'] | ||
>; | ||
|
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 guess optional chaining was troubling here 😆
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.
Yes the type narrowing seems to be necessary because the receiverParticipant is a combination of two types.