sorry, tried pasting
there is no coachId there now
As you say, the error disappears from the ts errors
even closing and reopening the file doesn't
@basarat: yes, right
It's not particularly easy to reproduce
I've even tried execing "linter:lint" command and even that doesn't fix it
and they are actively maintaing it :rose:
what I'm working on ^
typescript/register support
for node
does it?
If so I know I have a bug to find :) lately I haven't needed that
screenshot?
In my code
after the linter errors appeared, the ts errors got stuck as well (maybe)
just looking at my packages, I see I have linter and linter-tslint disabled
installed but disabled
Just a tip (that might help understand it better):
- ts errors are the source of truth .... they are sync matched with code editor changes by us
- linter errors cannot impact any other portion of our code paths. linter has a read only view of our state. But they may be out of sync
screenshot of the errors please. I want to see them before they become
7
remote debugging : - )