Skip to content

fix(language-service): update to use CompilerHost from compiler-cli #13189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 2, 2016

Conversation

chuckjaz
Copy link
Contributor

@chuckjaz chuckjaz commented Dec 1, 2016

What kind of change does this PR introduce? (check one with "x")

[x] Bugfix

What is the current behavior? (You can also link to an open issue here)

The language service used its own StaticReflectorHost which didn't have the auto-upgrade of metadata so it only worked for 2.3.0 projects.

What is the new behavior?

Use the compiler host from compiler-cli which includes the auto-upgrade of metadata allowing it to work on all 2.x.x projects.

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

@@ -0,0 +1,34 @@
{
"compilerOptions": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this new tsconfig file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default config does not produce files that are consumable from roll-up. This configuration creates a version of the module that can be rolled into the language service.

let report = (message: string) => {
results.push(
<Diagnostic>{kind: DiagnosticKind.Error, span: declaration.declarationSpan, message});
let report = (message: string, span?: Span) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

const?

@tbosch tbosch added action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews pr_state: LGTM labels Dec 2, 2016
@chuckjaz chuckjaz added action: merge The PR is ready for merge by the caretaker and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Dec 2, 2016
@alxhub alxhub merged commit 3ff6554 into angular:master Dec 2, 2016
maxime-allex pushed a commit to Linkurious/angular that referenced this pull request Dec 6, 2016
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants