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
feat(docs-site): thread consumer providers into the --site surface (#172)
The markdown docs surfaces load metadata via the sdk loadMemory({ providers }),
so `meta docs --model/--api` already honor a project's metaobjects.config.ts
`providers` (custom field/view/object subtypes). The HTML `--site` surface has
its OWN loader (docs-site's loadModel) with a hard-coded registry, so a model
using a consumer subtype (e.g. a custom `view.*` on a field) failed there alone
with `Unknown type "…" — not registered`, even though the config declared its
provider and every other surface resolved it.
- docs-site: loadModel(sourceDirs, extraProviders = []) composes the consumer
providers AFTER the built-in bundle (core-types/db/doc/prompt/ui), mirroring
loadMemory's `providers`; SiteOptions gains `extraProviders`; re-export
MetaDataTypeProvider. Additive — default none, so config-less callers are
unchanged (acme golden byte-identical).
- cli: emitSite threads the configProviders the docs command already loads from
metaobjects.config.ts into generateSite (both the site-only and the additive-
with-markdown paths), so `meta docs --site` resolves custom subtypes the same
way the markdown surfaces do.
Tests: docs-site provider-extension (a custom field subtype fails to load
without its provider, then resolves via extraProviders and renders a site); cli
docs-command reuses the existing custom-type project fixture to prove
`meta docs --site` now honors config providers. docs-site + cli typecheck clean.
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments