Where communities thrive
Join over
1.5M+ people
Join over
100K+ communities
Free
without limits
Create
your own community
Explore more communities
TypeStrong/atom-typescript
TypeScript workflow within Atom.io
People
Repo info
Activity
Jan 15 00:34
github-actions[bot]
closed
#1554
Jan 12 12:04
RamoFX
closed
#1568
Jan 08 03:35
aminya
edited
#1570
Jan 08 03:35
aminya
opened
#1570
Jan 01 00:16
github-actions[bot]
labeled
#1554
Dec 29 2020 09:23
lierdakil
closed
#1569
Dec 29 2020 09:23
lierdakil
labeled
#1569
Dec 27 2020 14:15
Ppang0405
opened
#1569
Dec 16 2020 13:08
RamoFX
edited
#1568
Dec 15 2020 17:57
RamoFX
edited
#1568
Dec 15 2020 15:42
RamoFX
edited
#1568
Dec 15 2020 15:41
RamoFX
edited
#1568
Dec 15 2020 15:29
RamoFX
edited
#1568
Dec 15 2020 15:29
RamoFX
edited
#1568
Dec 15 2020 15:26
RamoFX
opened
#1568
Nov 21 2020 21:35
delucca
closed
#1567
Nov 21 2020 00:22
lierdakil
labeled
#1567
Nov 21 2020 00:22
lierdakil
labeled
#1567
Nov 20 2020 13:54
lierdakil
labeled
#1566
Nov 20 2020 13:54
lierdakil
labeled
#1566
kpgarrod
@kpgarrod
sorry, tried pasting
Basarat Ali Syed
@basarat
@kpgarrod
press
cmd+s
does that fix it?
kpgarrod
@kpgarrod
You see, I have fixed the error at line 104
there is no coachId there now
As you say, the error disappears from the ts errors
Basarat Ali Syed
@basarat
"disappears from ts errors" "but sticks in linter errors" right?
kpgarrod
@kpgarrod
no, cmd+s does not fix it
even closing and reopening the file doesn't
@basarat
: yes, right
Basarat Ali Syed
@basarat
cool It's an issue with the
new linter rewrite
. I am hoping other lint clients (like us) will suffer the same fate and someone there will fix it :)
It's not particularly easy to reproduce
I've even tried execing "linter:lint" command and even that doesn't fix it
Cu3PO42
@Cu3PO42
:/
Basarat Ali Syed
@basarat
This is their gitter page btw :
https://gitter.im/AtomLinter/Linter
Cu3PO42
@Cu3PO42
The joys of being dependant on someone else fixing errors
Basarat Ali Syed
@basarat
we could put in the effort (its oss) ... just because nearly everybody who uses atom uses linter => they will get a clear issue report soon
and they are actively maintaing it :rose:
Cu3PO42
@Cu3PO42
Maybe I’ll look into it after I get sourcemaps working for the node debugger
Basarat Ali Syed
@basarat
what I'm working on ^
typescript/register
support
for node
Cu3PO42
@Cu3PO42
That’s awesome!
kpgarrod
@kpgarrod
@basarat
: actually, the typescript error doesn't always get cleared
_
Basarat Ali Syed
@basarat
@kpgarrod
ctrl+s
should clear that :
https://github.com/TypeStrong/atom-typescript#sync
does it?
If so I know I have a bug to find :) lately I haven't needed that
kpgarrod
@kpgarrod
no, it doesn't
Basarat Ali Syed
@basarat
:(
screenshot?
kpgarrod
@kpgarrod
Cu3PO42
@Cu3PO42
Can you consistently reproduce that?
kpgarrod
@kpgarrod
not sure, but it seems to be happening regularly
Basarat Ali Syed
@basarat
in a not so loud voice (at least its not a bug in linter then) ashamed
Cu3PO42
@Cu3PO42
Welp, I can’t seem to be able to reproduce that
In my code
kpgarrod
@kpgarrod
I just updated to 5.0.9 and the errors have gone for now
Cu3PO42
@Cu3PO42
Awesome!
kpgarrod
@kpgarrod
I'll try to watch out for the exact conditions that cause it if it happens again
Cu3PO42
@Cu3PO42
That’ll be great :)
kpgarrod
@kpgarrod
mmm, back again
Basarat Ali Syed
@basarat
screenshot ... before it goes too bad
kpgarrod
@kpgarrod
it seems that linter was still linting when the errors had disappeared
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
Basarat Ali Syed
@basarat
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 : - )
kpgarrod
@kpgarrod
well, I've uninstalled linter