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

[WIP]: Blocklist V2 #9435

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Conversation

pacyL2K19
Copy link
Contributor

@pacyL2K19 pacyL2K19 commented Jan 7, 2025

🚧 WIP

Fixing #8831

@pacyL2K19 pacyL2K19 marked this pull request as draft January 7, 2025 12:57
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This PR introduces a comprehensive blocklist management system with multi-level blocking capabilities (From/To, Cc, Bcc) and context-based state management.

  • Critical bug: Empty handler functions passed in SettingsAccountsBlocklistSection.tsx BlocklistContext.Provider instead of actual implementations
  • Added validation schema in SettingAccountBlocklistContactRow.tsx for email/domain inputs with proper error handling
  • New BlocklistItem type includes optional 'levels' property for granular blocking control
  • Implemented multi-select dropdown in SettingAccountBlocklistContactRow.tsx for configuring blocking levels
  • Created container architecture with SettingAccountsBlocklistContainer.tsx for better component organization

💡 (2/5) Greptile learns from your feedback when you react with 👍/👎!

8 file(s) reviewed, 8 comment(s)
Edit PR Review Bot Settings | Greptile

@@ -0,0 +1 @@
export type OptionalString = string | null;
Copy link
Contributor

Choose a reason for hiding this comment

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

style: Consider using undefined instead of null to align with TypeScript best practices, as undefined is more commonly used for optional values

@@ -0,0 +1,6 @@
export enum BlocklistContactLevel {
ALL = 'All',
FROMTO = 'From/To',
Copy link
Contributor

Choose a reason for hiding this comment

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

style: consider using 'FROM_TO' instead of 'FROMTO' to follow common enum naming conventions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants