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 : - )
and still have the problem
fwiw we will reinstall linter on next atom reboot ... so that will not help
now I'm not getting any errors at all!
@basarat I've noticed that
atom.d.ts in this repo differs significantly from the one in DefinitelyTyped. Some methods are missing, a lot of methods have been added (e.g. onDidChangeActivePaneItem and other event subscriptions). Is there a reason why they are maintained separately? Wouldn't it be better and easier for everybody to push changes from this repo to the main branch of DT?
Guys, great work! But wanted to ask what's happening with 5. releases? I have to press cmd+s two times to clear typescript errors. So basically I'm constantly pressing cmd+s to see if IO have any errors. Since 5. I have installed every release and then rolled back to 4.8.2 which is the latest one that works normally. I know it's probably connected with linter team, but any chance of fixing that? Thanks!
If I change it to
import from 'AuthorizeStep' it works.