-
Notifications
You must be signed in to change notification settings - Fork 41
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add the ability to emit index entries. (#271)
* Add the ability to emit index entries. I'm prototyping a Kythe TypeScript indexer plugin and things are fitting together pretty well. This starts by adding a method on the analyzer that will yield all of the information that the analyzer has determined about a file. I started with element and attribute references as they seem like the most valuable. What else could we emit here? * Add a test that `indexFile` creates a well-formed `HtmlNodeIndexEntry` for a locally defined element. * Add a test that element references are found across different files. * Test that entries are only generated for elements in template strings with a template tag named `html`. * Remove some empty lines. * Use `HtmlNodeKind` enum property instead of literal `"NODE"`. * Test that entries are created for attributes referencing properties. * Test that other types of attribute-position syntax produces references of the right kind. * Rename some tests. * Add more test cases for element references. * Add `name` for attribute entry definition targets. * Add tests that entries are created for different types of attribute definitions. * Use `type: Boolean` to define a property referenced by a boolean attribute. * Make `kind` a required property of `HtmlMemberBase`. * Use `.ts` for test files using types. * Add a change log entry. Co-authored-by: Peter Burns <rictic@google.com>
- Loading branch information
Showing
9 changed files
with
791 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.