angular-cn

Commit Graph

Author	SHA1	Message	Date
Andrew Scott	5cde4ad591	feat(language-service): add command for getting components for a template file (#40655 ) This commit adds a feature to the Angular Language Service that enables getting the locations for components that use a template file. Part of https://github.com/angular/vscode-ng-language-service/issues/1081 PR Close #40655	2021-02-04 10:47:22 -08:00
ayazhafiz	950875c1ba	refactor(language-service): pull out interfaces on package toplevel (#40621 ) Two motivations behind this change: 1. We would like to expose the types of the Language Service to external users (like the VSCode extension) via the npm package, on the top level of the package 2. We would like the View Engine and Ivy LS to share a common interface (notably after the inclusion of `getTcb`, the Ivy LS upholds a strict superset of `ts.LanguageService`; previously both VE and Ivy LS were aligned on `ts.LanguageService`.) To this end, this commit refactors the exports on the toplevel of the `language-service/` package to just be types common to both the VE and Ivy language services. The VE and Ivy build targets then import and use these types accordingly, and the expectation is that an external user will just import the relevant typings from the toplevel package without diving into either the VE or Ivy sources. Follow up on #40607 PR Close #40621	2021-02-03 09:19:54 -08:00

Author

SHA1

Message

Date

Andrew Scott

5cde4ad591

feat(language-service): add command for getting components for a template file (#40655 )

This commit adds a feature to the Angular Language Service that enables
getting the locations for components that use a template file.

Part of https://github.com/angular/vscode-ng-language-service/issues/1081

PR Close #40655

2021-02-04 10:47:22 -08:00

ayazhafiz

950875c1ba

refactor(language-service): pull out interfaces on package toplevel (#40621 )

Two motivations behind this change:

1. We would like to expose the types of the Language Service to external
   users (like the VSCode extension) via the npm package, on the top
   level of the package
2. We would like the View Engine and Ivy LS to share a common interface
   (notably after the inclusion of `getTcb`, the Ivy LS upholds a
   strict superset of `ts.LanguageService`; previously both VE and Ivy
   LS were aligned on `ts.LanguageService`.)

To this end, this commit refactors the exports on the toplevel of the
`language-service/` package to just be types common to both the VE and
Ivy language services. The VE and Ivy build targets then import and use
these types accordingly, and the expectation is that an external user
will just import the relevant typings from the toplevel package without
diving into either the VE or Ivy sources.

Follow up on #40607

PR Close #40621

2021-02-03 09:19:54 -08:00

2 Commits