Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 27 00:07
    github-actions[bot] closed #1546
  • Oct 21 09:39
    aminya opened #1565
  • Oct 21 00:07
    github-actions[bot] closed #1550
  • Oct 19 00:07
    github-actions[bot] labeled #1551
  • Oct 13 00:07
    github-actions[bot] labeled #1546
  • Oct 07 00:07
    github-actions[bot] labeled #1550
  • Oct 02 01:04
    lierdakil closed #1564
  • Oct 02 01:04
    lierdakil closed #1563
  • Oct 01 18:49
    lierdakil labeled #1564
  • Oct 01 18:49
    lierdakil labeled #1564
  • Oct 01 18:21
    nurdyguy opened #1564
  • Oct 01 18:16
    lierdakil closed #1559
  • Oct 01 18:02
    lierdakil labeled #1563
  • Oct 01 17:48
    hasenbalg opened #1563
  • Oct 01 17:15
    aminya synchronize #1559
  • Oct 01 16:09
    lierdakil closed #1558
  • Oct 01 16:06
    lierdakil closed #1560
  • Sep 30 16:13
    aminya synchronize #1560
  • Sep 30 16:09
    aminya synchronize #1560
  • Sep 30 16:06
    aminya synchronize #1559
Dandelion Mané
@decentralion
It feels almost like I must have it misconfigured somehow, since attaching all of the window properties to every single object doesn't make much sense
Basarat Ali Syed
@basarat

since attaching all of the window properties to every single object

@danmane Unclear what that means?

foo.n should not autocomplete NaN. Does it ?
Dandelion Mané
@decentralion
It does. Lemme grab a screenshot. one sce
blob
Micah Zoltu
@MicahZoltu
If I remember correctly, most of the annoyances with the auto-completer are due to the underlying auto-complete library.
I don't remember what it is called, but it is the thing Atom uses most places for auto-complete.
It is not nearly as good as the Visual Studio auto-complete UX.
Basarat Ali Syed
@basarat
blob
@danmane what other packages do you have ... that NaN is not ours
@danmane run apm ls
Other packages can use autocomplete + provide suggestions as well :)
Dandelion Mané
@decentralion
blob
/usr/local/google/home/danmane/.atom/packages (8)
├── .bin
├── atom-typescript@6.0.1
├── autoclose-html@0.18.0
├── autocomplete-polymer@0.2.4
├── color-picker@2.0.11
├── editorconfig@1.1.1
├── linter@1.5.0
└── merge-conflicts@1.3.5
maybe it's autocomplete polymer
Basarat Ali Syed
@basarat
@danmane only one way to be sure ... start disabling :)
Dandelion Mané
@decentralion
should disabling work immediately or do i need to reload somehow?
Basarat Ali Syed
@basarat
probably reload ... but use the keyboard shortcut : ctrl+alt+r on windows
Dandelion Mané
@decentralion
Yup. autocomplete-polymer was the culprit!
Thanks for the help :)
Btw, I greatly appreciate all of the software you've contributed for Typescript, as a frequent typescript dev it's aided me a lot over the past year. At this point seeing your name on a project gives me more confidence that I can depend on it, atom-typescript was a factor in my switching from sublime to atom
Basarat Ali Syed
@basarat
thanks :rose: :)
Dandelion Mané
@decentralion
@basarat if you are ever in the SF bay area id be happy to buy you a beer :) or a cappuccino, which is more to my taste. palo alto has some excellent coffee shops, although i hear the coffee in australia is quality as well
Basarat Ali Syed
@basarat
@danmane Thanks mate! For all your kindness :rose:
Jeon, TaeKyung
@greatelv
Is resolve atom-package dependencies issue ?
Basarat Ali Syed
@basarat
@wjswjs2 was. Just pushed a fix :rose: sorry about that
@wjswjs2 apm uninstall atom-typescript / apm install atom-typescript
Jeon, TaeKyung
@greatelv
thanks. always
Matt Mischuk
@mattmischuk
Is there a way to disable everything except syntax highlighting?
Basarat Ali Syed
@basarat
@mattmischuk there is this https://atom.io/packages/language-typescript-grammars-only by @tcarlsen
however you probably want the latest grammar work that @Cu3PO42 's been doing, ... so fork? Or PR / Issue ... guess there is a user demand for it ... so would be okay with maintaining it
look at atomConfig.ts in the repo ... if you create an issue I'll mark it up for grabs :rose:
Thomas Carlsen
@tcarlsen
would be nice with a grammar update :-)
Matt Mischuk
@mattmischuk
@basarat yeah that would be great because I don't need all of the features. :)
@tcarlsen are you going to create that issue? Should I?
Thomas Carlsen
@tcarlsen
Im going to update my package with the latest syntax and grammar. As I say in my README I love the work TypeStrong have done, but the package was to heavy for my taste
maybe splitting up atom-typescript into services (like autocomplete+ did) would be the best way?
but to answer your question,… You go ahead and create the issue :smile:
Thomas Carlsen
@tcarlsen
tcarlsen/language-typescript-grammars-only@e4f0ca7
released
Matt Mischuk
@mattmischuk
wow. released before I can even create an issue. Impressive.
Thomas Carlsen
@tcarlsen
@mattmischuk note that this is for my little language package only copy of atom-typescript.
Matt Mischuk
@mattmischuk
Of course, but it's still nice of you to do that so fast
Sebastian Lenz
@sebastian-lenz
Hi folks, got a little question. I've lowercased the filename of one of my source files, now atom complains that this file is not listed in tsconfig.json but on save it compiles the file with old camel cased name to the output directory. Syncing files does not help, so is there a something like a cache I can additionally clear?
Sebastian Lenz
@sebastian-lenz
Nevermind, was a TypeScript bug, opened an issue there.
Stephen Baynham
@CannibalVox
Hi, what are the best practices for writing a library in typescript that is then consumed by another typescript library? Is it really to manually ///<reference> the output file?
That seems not very robust...?
I'd like to use import from, but it seems like that's not compatible with the dts files produced by the typescript compiler
I'd have to manually edit those dts files I guess?
Stephen Baynham
@CannibalVox
Honestly I'm not particularly clear on how to do libraries generally, given the recommendation to not use --out.