Skip to content

Conversation

@dev-rb
Copy link
Contributor

@dev-rb dev-rb commented Jan 29, 2026

No description provided.

@github-actions
Copy link

github-actions bot commented Jan 29, 2026

page_size?: number;
}

interface EntitiesQueryRequesdtBody {
Copy link
Contributor

Choose a reason for hiding this comment

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

typo

Comment on lines 61 to 63
// ============================================================================
// Entity Type Filters
// ============================================================================
Copy link
Contributor

Choose a reason for hiding this comment

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

remove claudonian comment

Comment on lines +53 to +68

export const SoupViewContext = createContext<SoupViewContextValues>();

export const useSoupView = () => {
const context = useContext(SoupViewContext);

if (!context) {
throw new Error(
'useSoupView can only be used under a SoupViewContext.Provider'
);
}

return context;
};

export const useMaybeSoupView = () => useContext(SoupViewContext);
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe just use the createContextProvider from solid primitives ? or the asserted one ?

if (types.length === 0) types = [];
const includeArray: UnifiedSearchIndex[] = [];
for (const type of types) {
switch (type) {
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: uise ts-pattern's match

Comment on lines +81 to +93
// ============================================================================
// Lazy Initialization (avoids creating signals at module load time)
// ============================================================================

let _priorityLabelToggles: SignalToggle<string>[] | null = null;
let _priorityMetadataToggles: SignalToggle<EmailMetadataKey>[] | null = null;
let _depriorityLabelToggles: SignalToggle<string>[] | null = null;
let _depriorityMetadataToggles: SignalToggle<EmailMetadataKey>[] | null = null;

let _priorityLabels: Accessor<Set<string>> | null = null;
let _depriorityLabels: Accessor<Set<string>> | null = null;
let _priorityMetadata: Accessor<Set<EmailMetadataKey>> | null = null;
let _depriorityMetadata: Accessor<Set<EmailMetadataKey>> | null = null;
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems completely unnecessary.

readonly id: string;
readonly label: string;
readonly filterIds: readonly string[];
readonly allowMultiple?: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think allowMultiple is used. Would be nice to configure groups to not be mutually exclusive if we wanted to.

label: 'Mail',
predicate: emailFilter,
group: 'type',
shortcut: 'l',
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need the shortcuts here? Can't we let the hotkey logic handle deciding what filter gets bound to what key ?

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.

3 participants