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
{{ message }}
Repository navigation
Docs say top-level plugins apply to all spaces, but the config rejects them #190
docs/config.md (Plugins section) says plugins "can be declared at the top level (applies to all spaces) or per-space (overrides the top level)", and its example has a top-level plugins map. Core doesn't accept that.
measured: a .sctx.json with a top-level plugins key fails to load: Invalid config in …/.sctx.json: … "additionalProperty":"plugins" … "must NOT have additional properties". The config's JSON Schema (src/config/index.ts) allows plugins only on a space.
measured: everything that reads plugin config uses only context.space?.plugins (src/read/read-space.ts:6, src/render/render.ts:13, src/commands/template-sync.ts:6, src/commands/render.ts:94). Nothing merges a top-level map into the spaces.
Options
Fix the docs: plugin config is per space only. Remove the top-level example.
Implement the documented behaviour: accept a top-level plugins map, merge it into each space at load (with the space's entry winning per plugin), and keep the docs.
Option 2 is a convenience for configs with many spaces sharing a parse plugin's settings (a fieldMap, say). Option 1 is a one-line fix. Hosts like the Obsidian plugin look up a space's plugins["sctx-markdown"], so a merge at load time (option 2) would need no change there.
Activity