-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[$250] [Bug] Clean up confusing logic for when a report is exempt from being filtered out of the LHN #11481
Comments
Triggered auto assignment to @JmillsExpensify for Upwork job creation (chore: |
@JmillsExpensify can we get a C+ review for this, please? |
Sure thing, jumping in now! |
Current assignee @JmillsExpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Current assignee @tgolen is eligible for the External assigner, not assigning anyone new. |
Created the Upwork here: https://www.upwork.com/jobs/~01f59be4a13ee28103 |
Wait, @tgolen did we have a C+ review on this PR? I created an Upwork job but I'm not seeing any review in the linked PR. |
No it was merged before that. |
Cool. I'll close out the Upwork then, thank you! |
Problem
Coming from #10863 (comment)
The logic there is confusing and difficult to reason about.
Why is this important?
This makes the code hard to maintain.
Solution
Simplify and extract the logic to a separate method or break down the logic into several easier-to-read booleans.
The text was updated successfully, but these errors were encountered: