toeverything/AFFiNE · error · Error
Unsupported method: ${params.method}
Error message
Unsupported method: ${params.method} What it means
An exhaustive-switch fallback in the checkbox filter provider: filter$ only implements the 'is' and 'is-not' methods over the boolean custom property. It fires when a collection rule reaches this provider with any other method name, indicating a rule payload with a method this filter type does not support; the interpolated value is the unsupported method string from params.method.
Source
Thrown at packages/frontend/core/src/modules/collection-rules/impls/filters/checkbox.ts:45
}
return match;
})
);
}
if (method === 'is-not') {
return this.docsService.propertyValues$('custom:' + params.key).pipe(
map(o => {
const match = new Set<string>();
for (const [id, value] of o) {
if ((value === 'true' ? 'true' : 'false') !== params.value) {
match.add(id);
}
}
return match;
})
);
}
throw new Error(`Unsupported method: ${params.method}`);
}
}
View on GitHub (pinned to b4c8548c09)
Solutions
- Use one of the filter methods supported by the checkbox filter (e.g. is).
- Update the filter definition to a supported method.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown in the checkbox property filter when the filter method is neither 'is' nor 'is-not'.
Common situations: Occurs when a collection filter on a checkbox property uses an unknown comparison method, typically from stale or malformed filter config; re-create the filter with a supported method (is / is-not).
AI-assisted analysis of toeverything/AFFiNE@b4c8548c09 (2026-08-18).
Data as JSON: /api/errors/4ba89180643754b4.
Report an issue: GitHub.