Skip to content

feat: show filtered meta keys as adaptive collection columns - #77

Merged
d12frosted merged 1 commit into
masterfrom
feat/collection-filter-meta-columns
Sep 26, 2026
Merged

d12frosted merged 1 commit into
masterfrom
feat/collection-filter-meta-columns

Conversation

@d12frosted

Copy link
Copy Markdown
Owner

A collection view without :columns picks its columns from the notes it shows, but ignores the filter. So filtering by a field (rating:*, country:France, / m) never showed that field, and on notes without tags or todo the view was just Title and Backlinks. That looks broken, even though it's adaptive columns doing their thing.

Now every key in the filter's :meta conditions gets a (meta KEY) column, right after title and context. A key repeated in the filter gets one column. Views with explicit :columns and a fixed vulpea-ui-collection-default-columns are unchanged.

README, docstring and CHANGELOG are updated.

A collection view without :columns derives its columns from the notes
it shows, but never from the filter. A view filtered by a field, e.g.
rating:*, did not show that field, and over notes without tags or todo
it came up as just Title and Backlinks.

Every key in the filter's :meta conditions now gets a (meta KEY) column
after title and context. Views with explicit :columns are unchanged.
@d12frosted
d12frosted merged commit 2c6357f into master Sep 26, 2026
2 checks passed
@d12frosted
d12frosted deleted the feat/collection-filter-meta-columns branch September 26, 2026 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant