History

Alex Rickabaugh 4007422cc6 fix(compiler): correct confusion between field and property names (#38685 )

The `R3TargetBinder` accepts an interface for directive metadata which
declares types for `input` and `output` objects. These types convey the
mapping between the property names for an input or output and the
corresponding property name on the component class. Due to
`R3TargetBinder`'s requirements, this mapping was specified with property
names as keys and field names as values.

However, because of duck typing, this interface was accidentally satisifed
by the opposite mapping, of field names to property names, that was produced
in other parts of the compiler. This form more naturally represents the data
model for inputs.

Rather than accept the field -> property mapping and invert it, this commit
introduces a new abstraction for such mappings which is bidirectional,
eliminating the ambiguous plain object type. This mapping uses new,
unambiguous terminology ("class property name" and "binding property name")
and can be used to satisfy both the needs of the binder as well as those of
the template type-checker (field -> property).

A new test ensures that the input/output metadata produced by the compiler
during analysis is directly compatible with the binder via this unambiguous
new interface.

PR Close #38685

2020-09-08 11:43:02 -07:00

src

refactor(compiler): element.sourceSpan should span the outerHTML (#38581 )

2020-09-02 14:47:31 -07:00

test

fix(compiler): correct confusion between field and property names (#38685 )

2020-09-08 11:43:02 -07: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.