Skip to content
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

feat: filter by notification type #1860

Merged
merged 3 commits into from
Feb 26, 2025
Merged

feat: filter by notification type #1860

merged 3 commits into from
Feb 26, 2025

Conversation

setchy
Copy link
Member

@setchy setchy commented Feb 25, 2025

I figured while we're updating the Filters module, why not add the ability to filter by notification type

2025-02-25T13-03-14 802Z-Gitify-screenshot

Signed-off-by: Adam Setch <adam.setch@outlook.com>
@setchy setchy added this to the Release 6.2.0 milestone Feb 25, 2025
@github-actions github-actions bot added the enhancement New feature or enhancement to existing functionality label Feb 25, 2025
Signed-off-by: Adam Setch <adam.setch@outlook.com>
Signed-off-by: Adam Setch <adam.setch@outlook.com>
@setchy setchy merged commit a2ffd6c into main Feb 26, 2025
14 checks passed
@setchy setchy deleted the feat/filter-by-type branch February 26, 2025 12:36
@setchy
Copy link
Member Author

setchy commented Feb 26, 2025

Merging since this follows the current "pattern". Will work on reducing the duplication shortly

@@ -25,10 +25,7 @@ export const FILTERS_STATE_TYPES: Record<FilterStateType, TypeDetails> = {
title: 'Other',
description: 'Catch all for any other notification states',
},
} as Partial<Record<FilterStateType, TypeDetails>> as Record<
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's always satisfying dropping an as

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or enhancement to existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants