OptionalcomponentOptional resolver for dependency components referenced by name (+ optional
namespace + registry). Lint rules call this when a dep is location: 'registry' and the parent spec didn't denormalize the dep's props/events
inline — most commonly to verify props passed to a child component match
the child's declared property contract.
The linter never does I/O itself; it asks this resolver. Callers wire it however suits their side of the wire:
ComponentMetadataEngineServer.Instance.FindComponent(...)?.specIf absent, rules that rely on registry lookup degrade gracefully (they simply skip the cross-component check).
OptionalcomponentComponent spec being analyzed (linter walks code, dataRequirements, etc.).
OptionalcontextAuth/context — required by rules that resolve entity metadata.
OptionalentityOptional array of entity metadata providing complete field lists per entity. Used by the linter to validate field usage with two-tier severity:
If not provided, linter only checks against dataRequirements.fieldMetadata which may cause false-positive critical errors for valid but undeclared fields.
OptionalutilitiesRuntime utility hub forwarded to rules that need live metadata access (e.g. utilities.md.Entities). Optional — rules guard against absence.
Options accepted by the linter and individual lint rules at runtime.
This is a strict subset of the fields the linter actually reads — the companion
@memberjunction/react-test-harnesspackage extends this interface with browser-execution-specific fields (Playwright timeouts, onPageReady callbacks, etc.) that are irrelevant to static analysis.Keeping the linter's surface narrow avoids dragging Playwright-shaped options into server-side action callers that only want static checks.