Testing standards, patterns, and utilities for Graph Explorer including Vitest, DbState, renderHookWithState, test data factories, SPARQL test helpers, and backward compatibility testing for persisted data.

2026-04-24464

git

aws/graph-explorer

Git workflow conventions for Graph Explorer. Use when making commits, creating branches, or discussing version control practices.

2026-03-26464

github

aws/graph-explorer

Handle management of any GitHub related tasks, including creating or modifying issues, publishing a branch as a pull requests (or PRs), or creating or modifying sub-issues or child issues.

2026-03-19464

connectors

aws/graph-explorer

Database connector and explorer patterns for Gremlin, openCypher, and SPARQL, including the query template tag and escapeString usage.

2026-03-09464

product

aws/graph-explorer

Graph Explorer product overview including supported graph types, query languages, databases, key features, and high-level architecture.

2026-03-09464

react

aws/graph-explorer

React component patterns, hooks, naming conventions, and the query-language translation system for Graph Explorer.

2026-03-09464

name	typescript
description	TypeScript conventions and rules for Graph Explorer, including branded types, function style preferences, and type safety patterns.

TypeScript Conventions

General Rules

Do not change the VS Code setting typescript.autoClosingTags
Prefer named function syntax over anonymous arrow functions for module-level declarations (e.g., function handleClick() {} over const handleClick = () => {}). Arrow functions within function scope are fine.
Every commit should have no type errors
Use explicit type aliases instead of ReturnType<typeof ...> when available (e.g., use AppStore instead of ReturnType<typeof getAppStore>)

Branded Types

The project uses branded types from @/utils for type safety. These prevent accidental mixing of similar types at compile time.

Type	Creator Function	Location
`VertexId`	`createVertexId()`	`@/core/entities/vertex`
`VertexType`	`createVertexType()`	`@/core/entities/vertex`
`EdgeId`	`createEdgeId()`	`@/core/entities/edge`
`EdgeType`	`createEdgeType()`	`@/core/entities/edge`
`EdgeConnectionId`	`createEdgeConnectionId()`	`@/core/StateProvider/edgeConnectionId`
`ConfigurationId`	`createNewConfigurationId()`	`@/core/ConfigurationProvider/types`
`RenderedVertexId`	`toRenderedVertexId()`	`@/core/StateProvider/renderedEntities`
`RenderedEdgeId`	`toRenderedEdgeId()`	`@/core/StateProvider/renderedEntities`
`IriNamespace`	`splitIri()`	`@/utils/rdf`
`IriLocalValue`	`splitIri()`	`@/utils/rdf`
`RdfPrefix`	`generatePrefix()`	`@/utils/rdf`
`NormalizedIriNamespace`	`normalizeNamespace()`	`@/utils/rdf`

Always use the appropriate branded type instead of string when working with these identifiers.