-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Fix custom report field disappearing for submitter after report approval #95337
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
+119
−25
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
dca57d4
Fix report fields disappearing for submitter after report approval
MelvinBot b58ae3f
Remove now-unused CONST import
MelvinBot 42604eb
Add regression tests for report fields visibility after approval
MelvinBot ff93af8
Simplify report-field visibility conditions
MelvinBot 7ddf814
Remove unneeded explanatory comments on report-field visibility
MelvinBot 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
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.
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.
❌ CONSISTENCY-3 (docs)
After this change
isOnlyTitleFieldEnabledis defined assortedPolicyReportFields.every(shouldHideSingleReportField), which is exactly the expression still repeated insideshouldShowReportFieldon the line!sortedPolicyReportFields.every(shouldHideSingleReportField). That term now duplicates the derivedisOnlyTitleFieldEnabled— and the sameshouldShowReportFieldexpression already includes!isOnlyTitleFieldEnabled, so the.every(...)call recomputes an identical predicate over the same array.Reuse the derived value instead of recomputing it. Since
shouldShowReportFieldalready contains(!isCombinedReport || !isOnlyTitleFieldEnabled), the extra.every(...)term collapses to!isOnlyTitleFieldEnabledand can be dropped:(the last two lines can be merged into a single
!isOnlyTitleFieldEnabled).Reviewed at: 42604eb | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.