-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[CP Staging] Fix: Not here page opens when admin clicks Move expense in member's report #62611
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
2 commits
Select commit
Hold shift + click to select a range
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -45,21 +45,20 @@ type Props = { | |
function IOURequestEditReportCommon({backTo, transactionsReports, selectReport}: Props) { | ||
const {translate} = useLocalize(); | ||
const [allReports] = useOnyx(ONYXKEYS.COLLECTION.REPORT, {selector: (reports) => mapOnyxCollectionItems(reports, reportSelector), canBeMissing: true}); | ||
const [allPoliciesID] = useOnyx(ONYXKEYS.COLLECTION.POLICY, {selector: (policies) => mapOnyxCollectionItems(policies, (policy) => policy?.id), canBeMissing: false}); | ||
|
||
const currentUserPersonalDetails = useCurrentUserPersonalDetails(); | ||
const [searchValue, debouncedSearchValue, setSearchValue] = useDebouncedState(''); | ||
|
||
const expenseReports = useMemo( | ||
() => | ||
Object.values(allPoliciesID ?? {}).flatMap((policyID) => { | ||
if (!policyID) { | ||
Object.values(transactionsReports ?? {}).flatMap((transactionsReport) => { | ||
if (!transactionsReport.policyID) { | ||
luacmartins marked this conversation as resolved.
Show resolved
Hide resolved
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. Same here. This is fine for this PR since we're CPing it, but unreported transactions won't have a policyID, so this will return nothing. |
||
return []; | ||
} | ||
const reports = getOutstandingReportsForUser(policyID, currentUserPersonalDetails.accountID, allReports ?? {}); | ||
const reports = getOutstandingReportsForUser(transactionsReport.policyID, transactionsReport?.ownerAccountID ?? currentUserPersonalDetails.accountID, allReports ?? {}); | ||
return reports; | ||
}), | ||
[allPoliciesID, allReports, currentUserPersonalDetails.accountID], | ||
[allReports, currentUserPersonalDetails.accountID, transactionsReports], | ||
); | ||
|
||
const reportOptions: ReportListItem[] = useMemo(() => { | ||
|
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.
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 think this is ok for now since we'll CP this PR, but ultimately we also want to handle the case where the user has 1 available report and the available reportID is not the same as the transaction.reportID. Basically this flow:
Report
field, but not edit it even though the user has an available report