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.
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
Load parent report action from withOnyx in ReportActionItem #34057
Load parent report action from withOnyx in ReportActionItem #34057
Changes from 1 commit
33c40c5
e3758e0
1470c83
c89290b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Are we sure we will have a report? I assume yes. But it's a little ambiguous because you have a conditional on line 776 that does:
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.
The proptypes declare that
report
is required, as well as in both of the parents that use this component, so I am confident in expectingreport
to always be there (though I know it's not a guarantee). The only reason there is a conditional on 776 is because I copied it from other components. I'll remove the conditional down there.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.
For a little extra context, I did look into subscribing to this higher up in the component tree, but it got pretty convoluted and went all the way up to
ReportScreen
. Interestingly enough, I have this PR whereReportScreen
is now subscribing to the parent report action... so if we really wanted to, we could pass theparentReportAction
all the way down as a prop. It would be a bigger change, but it might have less of a possible performance impact on this component (which looks to be highly optimized).