feat(website): allow restricting which fields are allowed to be referenced in the AdvancedQueryFilter

[fhennig]

resolves #1157, #1194

Summary

Adds an optional allowedFields config to the advancedQuery baseline filter. When set, the parsed LAPIS expression is walked client-side after successful validation, and any metadata column not in the allowed list causes an error with an informative message. Mutation-only queries (e.g. A123T) always pass regardless of allowedFields, since they reference sequence positions rather than metadata columns.

• New AdvancedQueryFilterConfig type exported from BaselineSelector.tsx with optional allowedFields?: string[]
• AdvancedQueryFilter component accepts and enforces allowedFields in its onSuccess handler via extractMetadataFields
• New extractMetadataFields utility in siloFilterExpression.ts recursively collects all column values from a SiloFilterExpression tree
• Three browser spec tests covering: disallowed field → error, allowed field → checkmark + callback, mutation-only → checkmark

The feature is fully opt-in: omitting allowedFields preserves existing behaviour (any field is allowed).

Test plan

• extractMetadataFields unit tests in siloFilterExpression.spec.ts
• Browser spec tests for the three allowedFields scenarios in AdvancedQueryFilter.browser.spec.tsx
• Manually tested by temporarily setting allowedFields: ['host'] on the COVID baseline config — queries on host passed, queries on other metadata fields showed the error, mutation queries passed

PR Checklist

• All necessary documentation has been adapted.
• The implemented feature is covered by an appropriate test.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboards	Ready	Preview, Comment	May 5, 2026 8:49am