Extends the conformance ESLint layer with the consent-check rule:
- `no-undeclared-consent-check` (warn): `consent.isGranted("X")` in a
use-case file must match a category declared in `manifest.requiresConsent`;
also warns when requiresConsent is declared but no isGranted call is found.
- `_manifest-ast.js`: adds `parseManifestFully` which extracts top-level
`name`, `requiredCores`, `requiresConsent`, and per-use-case maps from the
manifest AST; `requiresConsent` extraction tested in `_manifest-ast.test.js`.
- `_rule-context.js` / `_rule-schema.js`: shared helpers extracted from the
existing per-rule files so the new rule can resolve use-case name + feature
root without duplication.
- Existing rules (`no-undeclared-audit`, `no-undeclared-event-publish`,
`no-undeclared-analytics-event`) updated to use the shared helpers.
- `plugin.js` + `base.js` register the rule at warn severity.
- CLAUDE.md + conformance-quickref.md: rule count advanced from 11 → 12.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
19 lines
760 B
JavaScript
19 lines
760 B
JavaScript
import { useCaseNameFromFile } from "./_usecase-name.js";
|
|
import { featureRootForFile } from "./_manifest-source.js";
|
|
|
|
/**
|
|
* Resolves the rule execution context from an ESLint context object.
|
|
* Returns null when the file is not a use-case file or not inside a
|
|
* recognised feature package — callers should return {} immediately.
|
|
*/
|
|
export function resolveRuleContext(context) {
|
|
const opts = context.options[0] ?? {};
|
|
const repoRoot = opts.repoRoot ?? context.cwd ?? process.cwd();
|
|
const filename = context.filename;
|
|
const useCaseName = useCaseNameFromFile(filename);
|
|
if (!useCaseName) return null;
|
|
const featureRoot = featureRootForFile(filename, repoRoot);
|
|
if (!featureRoot) return null;
|
|
return { useCaseName, featureRoot, repoRoot };
|
|
}
|