-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[WEB-1671] fix: expired snooze issues fixed #5270
Conversation
WalkthroughThe recent changes enhance the responsiveness and filtering logic of the inbox issue management system. The Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant InboxIssueStatus
participant ProjectInboxStore
User->>ProjectInboxStore: Request filtered inbox issues
ProjectInboxStore->>ProjectInboxStore: Evaluate conditions
alt Conditions met
ProjectInboxStore-->>User: Return relevant issues
else Conditions not met
ProjectInboxStore-->>User: Return empty results
end
User->>InboxIssueStatus: Render inbox issue status
alt Snoozed date passed or detail not found
InboxIssueStatus-->>User: Render empty fragment
else Active issue
InboxIssueStatus-->>User: Display issue details
end
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- web/core/components/inbox/inbox-issue-status.tsx (1 hunks)
- web/core/store/inbox/project-inbox.store.ts (2 hunks)
Additional comments not posted (5)
web/core/components/inbox/inbox-issue-status.tsx (2)
22-22
: Ensure the correctness of the new condition.The new condition
isSnoozedDatePassed
is crucial for determining if the snoozed date has passed. Ensure that the condition is accurate and handles edge cases, such as invalid dates.
22-22
: LGTM! The new condition enhances the component's responsiveness.The new condition
isSnoozedDatePassed
is appropriately used within the component's control flow to ensure that only relevant information is displayed when the issue is active.web/core/store/inbox/project-inbox.store.ts (3)
159-159
: Ensure the correctness of the new variable.The new variable
currentTime
is crucial for determining the current timestamp. Ensure that the variable is accurate and handles edge cases, such as time zone differences.
161-174
: LGTM! The new conditions enhance the filtering logic.The new conditions are appropriately used within the method's control flow to ensure that only issues that are actively snoozed or have exceeded their snooze duration are included in the filtered results.
311-313
: Ensure the correctness of the new status inclusion.The new status inclusion logic ensures that snoozed issues are considered in the filtering process. Ensure that the logic is accurate and handles edge cases, such as missing statuses.
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- web/core/store/inbox/project-inbox.store.ts (2 hunks)
Additional comments not posted (3)
web/core/store/inbox/project-inbox.store.ts (3)
159-159
: Introduction ofcurrentTime
is appropriate.The introduction of the
currentTime
variable is a good practice to capture the current timestamp for use in filtering logic.
313-315
: Inclusion ofSNOOZED
status is appropriate.Including the
SNOOZED
status in thestatus
variable ensures that snoozed issues are considered in the query parameters for fetching inbox issues.
161-175
: Updated filtering logic looks good but verify correctness.The updated filtering logic for
filteredInboxIssueIds
appears correct, ensuring that actively snoozed issues and those with expired snooze durations are handled appropriately.Please verify the logic with unit tests to ensure correctness.
Summary
Snoozed issues with a past due date continue to display "-x days to go" after the intended snooze date has passed. These issues should no longer be considered snoozed and should be displayed under inbox issues window and time stamp -x days should be removed
[WEB-1671]
Summary by CodeRabbit
New Features
Bug Fixes