Reference on AngularTS

Find the right documentation

Mon, 01 Jan 0001 00:00:00 +0000

Use documentation by intent:

New to AngularTS: start with Get started, then complete the task-board tutorial.
Building a feature: use Guides for forms, routing, server data, testing, and production.
Choosing an architecture: use Choose an approach.
Learning a concept: use Concepts.
Looking up behavior: use singular directive, service, filter, and value reference sections.
Using another language: use Integrations.
Fixing a failure: start with the error catalog and troubleshooting guide.

Plural sections such as Directives and Services teach workflows. Singular sections such as Directive and Service are feature reference.

How to use the API reference

Mon, 01 Jan 0001 00:00:00 +0000

Find the API category

An ng-* HTML name is usually a directive. A name injected into a function is a service or value token. A capitalized TypeScript name is a generated type.

Read a TypeScript signature

value?: string means the property is optional and, when supplied, must be a string. string | null means either value is accepted. () => void means a function takes no arguments and returns no useful value. Array<T> means an array whose items have type T.

Error and symptom catalog

Mon, 01 Jan 0001 00:00:00 +0000

Application does not bootstrap

Check that the bootstrapped module name matches the registered module, the root exists, and AngularTS is loaded once. Do not bootstrap on ng-if, ng-include, or ng-view.

Unknown provider or injection token

Confirm the provider is registered before use, its module is in the dependency graph, and the token spelling is correct. Regenerate language bindings after changing the public namespace.

State changed but the view did not

Read the value through a reactive binding. In typed views, use a reader such as () => controller.value. In keyed collections, call the item reader.

Public feature coverage

Mon, 01 Jan 0001 00:00:00 +0000

Every shipped directive module, service module, filter module, public injection token, and built-in configuration key must map to documentation.

A mapping is either:

Dedicated: the page documents that feature directly.
Canonical: a broader page owns the feature as part of one workflow.

The mapping is stored in docs/public-feature-docs.json. CI discovers the source surface and fails when a module or public token changes without updated documentation ownership.

Utility, worker, WebAssembly, and transport helpers are documented at their user-facing boundary rather than by internal source file. Generated TypeScript API pages remain the authoritative signature reference; guides explain when and why to use those signatures.