TypeStrong/atom-typescript

TypeScript workflow within Atom.io

Dandelion Mané

@decentralion

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.

Basarat Ali Syed

@basarat

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?

@CannibalVox No just use commonjs with declaration true. A quickstart : http://basarat.gitbooks.io/typescript/content/docs/node/nodejs.html

Stephen Baynham

@CannibalVox

@basarat Error message says it's not a module, because the DTS files being produced by typescript aren't really ambient modules it seems?

Stephen Baynham

@CannibalVox

I guess I can have gulp place an ambient declaration before & after the DTS output, is that the best way? Seems crazy that I have to do a full gulp build, deploy, update to have two projects open in Atom, one of which relies on the other.

Also is there any way to not compile to a single file but have the compiled output not be mixed in with the source?

Basarat Ali Syed

@basarat

because the DTS files being produced by typescript aren't really ambient modules it seems?

They should be. Should have stuff like export var at the root level of the file .... that makes them an ambient export module

Also is there any way to not compile to a single file but have the compiled output not be mixed in with the source?

You can use outDir. But I recommend against that as it becomes fairly weird ... fairly quickly

Stephen Baynham

@CannibalVox

All that's at the root level is declare namespace

because the root of my source files looks like this:

namespace TechnicCommon {
export class VersionedResource extends WebResource {

is that not correct?

Basarat Ali Syed

@basarat

is that not correct?

No. export needs to be at the root level . (ref)

Stephen Baynham

@CannibalVox

But http://basarat.gitbooks.io/typescript/content/docs/project/namespaces.html shows quite the opposite

Basarat Ali Syed

@basarat

@CannibalVox at the bottom of that page

For most projects we recommend using external modules and using namespace for quick demos and porting old JavaScript code.

Stephen Baynham

@CannibalVox

Okay, I have two classes that are in the same exported module, one inherits from the other and both need to be available to consumers. I've tried marking just the module for export, but in that case the class doesn't appear in the DTS file. If I mark the class for export, though, it's not marked as export in the DTS file. This seems like it's probably fine, but when compiling the child class it gives me an "all export or all local" error. This happens even when I'm importing directly from the TS file, though.

Where communities thrive

People

Repo info

Activity