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
Showing error "cannot read property 'isSkipSelf' of null" and does not validate templates #181
Comments
probably related to #183 |
Can you produce a project that reproduces this and supply a link to the repository? |
Also facing this and it's happening in a lot of places. Renders the whole service unusable in the template, and very obtrusive. |
@chuckjaz do you still need repro? |
it will take me sometime to get this setup on repo. basically this is happening when you reference package libraries that are part of your repo and we update master tsconfig paths section to setup the definitions. Ex: tsconfig |
Any news on this? it's annoying :( |
This stopped happening after updating everything to latest. @matheo maybe check that you have updated the language service extension. |
Just run on the same error after fixing the component TS import, the template error was gone it would be nice to have better error message in this case |
@mrahhal I had the latest extension version |
Happened to me after moving a component and some classes to a different folder. |
I disabled/reloaded and enabled/reloaded Angular Language Service and the error disappeared |
I get the same error in VS Code (most recent version). |
Using WebStorm, uninstalling @angular/language-service from the project fixed the problem (and no functionality seems to be lost) |
Didn't work for me unfortunately in WebStorm |
same error here on a random file... any way to diagnose? |
I was able to solve my issue installing the peerDependencies in the project containing my library. Somehow angular or material are interfering |
Write the full dependency path(instead of reading it from a folder) which resolves my issue in Angular 6 |
This error started happening randomly on a project (and templates that haven't been modified since) that was working perfectly with VS Code previous version. |
For me unmet peer dependencies caused the problem. After installing them and restarting window everything is resolved. |
I got the same issue after installed "Paste JSON as Code" extension in Visual Code. Disabled this extension fix for me the problem. |
It happened to me today after adding a new dependency. Deleting node_modules and re-installing the packages solved it. |
Just restart your machine after install all the dependencies. |
worked for me!!! |
As others have said, the error is probably coming from somewhere else, it's just an unhelpful error message. What helped me, was running the native TS compiler ( |
Please tell me how to disable whatever it is that is causing the rendering of the red squigglies in my code. |
Today I saw this error after confusing an @Input()
public title: string;
constructor() {} but for some reason I wrote constructor(public title: string) {} Is it possible to generate a more helpful message in this case? |
The original issue |
Just close your vs code editor and reopen.It worked for me. |
Restart VS Code solved the error for me, not sure what happen but it just disappeared |
How I was able to solve this problem was to update the import statement for a service in my component file, please check your imports :) |
Check that all modules in your template file with the error are imported. That was my mistake. |
One more "it worked for me" tip: Make sure |
Close and reopen the VSCode |
This was fixed in angular/angular#30075 |
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. |
Using
VSCode v1.17.1
Workspace typescript v2.5.3
Workspace Angular v4.4.4
instead of showing template validation messages, language service extension is showing below error
"Cannot read property 'isSkipSelf' of null"
The text was updated successfully, but these errors were encountered: