History

Alex Rickabaugh c55bf4a4a3 refactor(compiler-cli): identify structural directives (#40032 )

This commit introduces an `isStructural` flag on directive metadata, which
is `true` if the directive injects `TemplateRef` (and thus is at least
theoretically usable as a structural directive). The flag is not used for
anything currently, but will be utilized by the Language Service to offer
better autocompletion results for structural directives.

PR Close #40032

2020-12-14 12:08:41 -08:00

src

refactor(compiler-cli): implement DeclarationNode node type (#38959 )

2020-10-12 08:32:46 -07:00

test

refactor(compiler-cli): identify structural directives (#40032 )

2020-12-14 12:08:41 -08:00

BUILD.bazel

feat(ivy): integrate indexing pipeline with NgtscProgram (#31151 )

2019-06-24 18:47:56 -07:00

index.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:26:58 -04:00

README.md

docs(ivy): Add README to indexer module (#31260 )

2019-07-31 11:37:11 -07:00

README.md

`indexer`

The indexer module generates semantic analysis about components used in an Angular project. The module is consumed by a semantic analysis API on an Angular program, which can be invoked separately from the regular Angular compilation pipeline.

The module is not a fully-featured source code indexer. Rather, it is designed to produce semantic information about an Angular project that can then be used by language analysis tools to generate, for example, cross-references in Angular templates.

The indexer module is developed primarily with the Kythe ecosystem in mind as an indexing service.

Scope of Analysis

The scope of analysis performed by the module includes

indexing template syntax identifiers in a component template
generating information about directives used in a template
generating metadata about component and template source files

The module does not support indexing TypeScript source code.