You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updating scope based on work on #72 (knowledge wiki) and #78 (metadata layout).
The first bullet — files in path x have type y — is now the most immediately useful parsing hint. Two knowledge wiki spaces have been configured using the same knowledge_wiki schema. Right now they rely on schema-level aliases for type resolution, but folder-to-type mapping at the space config level would be cleaner.
Where fromFolder: true auto-maps folder names to type names (matching on type name, aliases, or matchers from the schema), and overrides handle cases where folder names don't match.
This connects to #73 (type inference from folder structure) which proposes this as a plugin-level config, and #78 which discusses separating type configuration from relationships in the schema metadata.
Also noting the other hint types (embedded nodes from headings, normalising titles) can stay low priority — they're useful but less immediately needed.
Activity
mindsocket commentedon Apr 6, 2026
Updating scope based on work on #72 (knowledge wiki) and #78 (metadata layout).
The first bullet —
files in path x have type y— is now the most immediately useful parsing hint. Two knowledge wiki spaces have been configured using the same knowledge_wiki schema. Right now they rely on schema-level aliases for type resolution, but folder-to-type mapping at the space config level would be cleaner.This could take the form:
{ "name": "my-wiki", "path": "...", "schema": "knowledge_wiki.json", "plugins": { "markdown": { "typeInference": { "fromFolder": true, "overrides": { "Research": "source", "Personal": "note" } } } } }Where
fromFolder: trueauto-maps folder names to type names (matching on type name, aliases, or matchers from the schema), andoverrideshandle cases where folder names don't match.This connects to #73 (type inference from folder structure) which proposes this as a plugin-level config, and #78 which discusses separating type configuration from relationships in the schema metadata.
Also noting the other hint types (embedded nodes from headings, normalising titles) can stay low priority — they're useful but less immediately needed.
feat: folder-based type inference for markdown plugin
feat: folder-based type inference for markdown plugin