Skip to content

Conversation

ayazhafiz
Copy link
Contributor

This commit elaborates diagnostics produced for invalid template
contexts by including the name of the embedded template type using the
template context, and in the common case that the implicity property is
being referenced (e.g. in a for .. of .. expression), suggesting to
refine the type of the context. This suggestion is provided because
users will sometimes use a base class as the type of the context in the
embedded view, and a more specific context later on (e.g. in an
ngOnChanges method).

Closes angular/vscode-ng-language-service#251

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Feature

Does this PR introduce a breaking change?

  • Yes
  • No

@ayazhafiz ayazhafiz added feature Issue that requests a new feature area: language-service Issues related to Angular's VS Code language service target: patch This PR is targeted for the next patch release labels Jan 12, 2020
@ayazhafiz ayazhafiz requested a review from kyliau January 12, 2020 22:22
@ayazhafiz ayazhafiz requested a review from a team as a code owner January 12, 2020 22:22
@ngbot ngbot bot modified the milestone: needsTriage Jan 12, 2020
@ayazhafiz ayazhafiz requested a review from kyliau January 14, 2020 03:10
ayazhafiz and others added 2 commits January 22, 2020 19:29
This commit elaborates diagnostics produced for invalid template
contexts by including the name of the embedded template type using the
template context, and in the common case that the implicity property is
being referenced (e.g. in a `for .. of ..` expression), suggesting to
refine the type of the context. This suggestion is provided because
users will sometimes use a base class as the type of the context in the
embedded view, and a more specific context later on (e.g. in an
`ngOnChanges` method).

Closes angular/vscode-ng-language-service#251
@ayazhafiz ayazhafiz force-pushed the e/template-context-diag-msg branch from 8a1c4c6 to 2fb0a95 Compare January 23, 2020 03:40
@kyliau kyliau added the action: merge The PR is ready for merge by the caretaker label Jan 23, 2020
AndrewKushnir pushed a commit that referenced this pull request Jan 23, 2020
…gs (#34751)

This commit elaborates diagnostics produced for invalid template
contexts by including the name of the embedded template type using the
template context, and in the common case that the implicity property is
being referenced (e.g. in a `for .. of ..` expression), suggesting to
refine the type of the context. This suggestion is provided because
users will sometimes use a base class as the type of the context in the
embedded view, and a more specific context later on (e.g. in an
`ngOnChanges` method).

Closes angular/vscode-ng-language-service#251

PR Close #34751
@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 Feb 23, 2020
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 area: language-service Issues related to Angular's VS Code language service cla: yes feature Issue that requests a new feature target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Angular] The template context does not have an implicit value
3 participants