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
Document compiler flag fullTemplateTypeCheck
(at least in Release Notes)
#19681
Comments
fullTemplateCodegen
(at least in Release Notes)
We have a new compiler setting called This setting will become the default in Angular 6, and is highly recommended. We didn't turn in on in Angular 5 to not break existing users. I.e. the behavior you are seeing here is exactly what users saw in Angular 4. This works as intended, but somehow we forgot to document this. Keeping the bug open to track that we need to document this. |
Oh, there is a bug with |
The flag is only available in Angular 5 and later, or its also available in V4? |
Yes
…On Fri, Oct 13, 2017 at 8:13 AM, Alan Agius ***@***.***> wrote:
The flag is only available in Angular 5 or later?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#19681 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAqKf-zxpsc2GXN8NVpUvNLgdMYBXODAks5sr34EgaJpZM4P2sTg>
.
|
fullTemplateCodegen
(at least in Release Notes)fullTemplateTypeCheck
(at least in Release Notes)
We should first rollout |
|
Why was this closed? |
@mgol It was documented some time ago: https://angular.io/guide/aot-compiler#fulltemplatetypecheck |
Hmm, OK. I wonder why @chuckjaz wrote it's not documented just before closing then. |
-t+w ;)
…On Thu, Feb 8, 2018, 12:45 Michał Gołębiowski-Owczarek < ***@***.***> wrote:
Hmm, OK. I wonder why @chuckjaz <https://github.com/chuckjaz> wrote it's
not documented just before closing then.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#19681 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARAoAJplp0ejylVY93eOA2vdUQIHM-Tks5tSt5zgaJpZM4P2sTg>
.
|
Sorry. Yes. It is now documented. Sorry for the typo. |
Has this already been done? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm submitting a...
Current behavior
In my html view I am referring a variable that it doesn't exist, This won't be catched unless someone consumes my library.
I am using NGC bin directly to compile my TS to NGC.
in the ngfactory.ts I can see that there is an error, however this is not emitted on compilation
Expected behavior
When compiling with NGC it should throw an error while compiling
Minimal reproduction of the problem with instructions
https://github.com/alan-agius4/angular-ngc-template-error
What is the motivation / use case for changing the behavior?
It should throw an error
Environment
For Tooling issues:
Others:
The text was updated successfully, but these errors were encountered: