Interface ValidationContext

Name of the component being validated

Example: "DataGrid", "EntityDataGrid", "SimpleChart"

Full component specification

Provides access to:

• Type definitions (for custom type validation)
• Data requirements (entities, queries)
• Other properties (for cross-property validation)
• Dependency specs (for validating nested components)

SQL dialect for WHERE clause parsing and validation.

Used by the SqlWhereClauseValidator to parse SQL with the correct syntax for the target database platform (SQL Server, PostgreSQL, etc.). If not provided, the validator falls back to SQL Server dialect.

Map of entity name to entity metadata

Populated from componentSpec.dataRequirements.entities Used by validators that check field names, entity references, etc.

Example:

const memberEntity = entities.get('Members');
const fields = memberEntity.fields; // Array of EntityFieldInfo
Copy

The AST node being validated

This is typically the JSXAttribute node, but validators can traverse to child nodes for more specific location information.

Babel traversal path for the node

Provides access to parent nodes, scope information, and AST manipulation. Validators should not modify the AST - this is read-only validation.

Name of the property being validated

Example: "fields", "columns", "entityName", "extraFilter"

Whether the parent passed the property on the element.

The linter sets this on every context it builds. It is false only for a validator that opted in with SemanticValidator.EvaluatesAbsentProp; then propertyValue is undefined and Node is the element's opening tag. Optional so contexts built outside the linter (tests, other tools) stay valid.

Extracted value of the property

This is the result of PropValueExtractor.extract() and can be:

• Primitive: string, number, boolean, null
• Array: Array of extracted values
• Object: Record<string, ExtractedValue>
• DynamicValue: { _type: 'identifier' | 'expression', name?, description? }

If the value is a DynamicValue, validators should typically skip validation and return an empty violations array (the linter will warn the user).

Map of query name to query metadata

Populated from componentSpec.dataRequirements.queries Used by validators that check query references and parameters.

Example:

const query = queries.get('Sales by Region');
const params = query.parameters; // Array of QueryParameter
Copy

Map of sibling props on the same JSX element

Key is prop name, value is extracted value. Used for constraints with dependsOn to access related prop values.

Example:

// <EntityDataGrid entityName="Members" fields={['FirstName', 'LastName']} />
siblingProps.get('entityName') // => "Members"
siblingProps.get('fields') // => ['FirstName', 'LastName']
Copy

Type inference engine for checking expression types

Used for advanced type checking beyond what PropValueExtractor provides. Can infer types of variables, function calls, etc.