TypeStrong/atom-typescript

TypeScript workflow within Atom.io

Miguel Couto

@Mig1st4ck

something like this.

__metadata('design:paramtypes', [, Object, Object, Object, .., Object, Object, ..., ., ., ., Object])

my Constructor for the class is this


    constructor($stateParams,
      private $state: ng.ui.IStateService,
      private $scope: ng.IScope,
      private common: Common.ICommonService,
      private  docsData: Lf.Docs.DocsService,
      private docsTransform: Lf.Docs.ITransfomDocHelper,
      private modal: Bootstrap.Modal,
      private  calcs: Lf.Docs.Editor.CalcFactory,
      private editorChanges: Editor.EditorChanges,
      private editorCanAct: Editor.EditorCanAct,
      private docTransfLines: Editor.ModalTransformLines,
      private  helperNewDoc: Docs.INewDocHelper) {

Aviel Fedida

@avielfedida

When installed 5.5.0, the plugin won't compile, when cheacked config.cson, I notice that: "atom-typescript": {}

Basarat Ali Syed

@basarat

when cheacked config.cson, I notice that: "atom-typescript": {}

@avielfedida That's just because you don't have any settings saved for atom-typescript. Should be a correlation with wont' compile. Can you provide more info :rose:

Philipp Knecht

@fopsdev

hi all, i'm checking out aurelia together with typescript. i have typestrong 5.5.1 installed. but the build somehow does not finish
if somebody wants to check it out: https://github.com/fopsdev/aurelia-typescript.git

Philipp Knecht

@fopsdev

i'm on a nightly tsc build
and yes, i'm sure i'm doing some things wrong :)

Aviel Fedida

@avielfedida

@basarat After updated to 5.5.1 all is working :smile: Thanks

Basarat Ali Syed

@basarat

@avielfedida yeah atom updates are dodgy

@fopsdev I pressed f6 to build

too many issues to provide meaningful help

Philipp Knecht

@fopsdev

@basarat i see... yeah i found some strange definitions as well. first those guys needs to be fixed. thanks for diving in i'll give it a try

Basarat Ali Syed

@basarat

thanks :rose:

Valentin Robert

@Ptival

@basarat I don't see any error, I'm not sure how to check whether atom-typescript even tries to do anything...

@basarat and the message about dependencies never appears (not even the one that says to wait)

Valentin Robert

@Ptival

@basarat everything works on 4.5.0, nothing works on 5.5.0 and 6.0.0

Basarat Ali Syed

@basarat

I don't see any error, I'm not sure how to check whether atom-typescript even tries to do anything

@Ptival Check the console ctrl+alt+i will open the dev tools

Valentin Robert

@Ptival

@basarat yeah, nothing TS-related shows up in the Dev console

is there an easy way to see what is happening?

Basarat Ali Syed

@basarat

@Ptival you can setup a dev enviroment quite easily : https://github.com/TypeStrong/atom-typescript/blob/master/CONTRIBUTING.md#setup-dev-machine

Some debugging docs https://github.com/TypeStrong/atom-typescript/blob/master/CONTRIBUTING.md#debugging

Valentin Robert

@Ptival

@basarat Thanks, I'll look into that

Valentin Robert

@Ptival

@basarat ever seen this happen? http://i.imgur.com/hR3Lqri.jpg

Basarat Ali Syed

@basarat

@Ptival nope. Seems like a bug in underscore definitions. I personally haven't used underscore for quite a while.

Rob Yoder

@robyoder

So the whole <span class="badge"… is not just me… Is there a way to make that display as it was apparently intended instead of being rendered to a string?

Basarat Ali Syed

@basarat

Is there a way to make that display as it was apparently intended instead of being rendered to a strin

I think @nycdotnet just fixed it TypeStrong/atom-typescript@0bee436

Rob Yoder

@robyoder

Oh, awesome

Erik Schilling

@Ablu

Hello. My pending request cout goes up for ever which results in all actions taking forever to complete (navigations like go to definition do not work): https://dl.dropboxusercontent.com/u/45541625/2015-09-05-222751_74x37_scrot.png
Any idea why this could happen?

Sometimes it manages to complete the stuff, but usually it keeps hanging...

My tsconfig.json:

{
    "version": "1.5.0",
    "compilerOptions": {
        "emitDecoratorMetadata": true,
        "experimentalDecorators": true,
        "target": "es5",
        "module": "commonjs",
        "declaration": false,
        "noImplicitAny": false,
        "removeComments": true,
        "noLib": false,
        "outDir": "dist/js/cjs"
    },
    "fileGlobs": [
        "./modules/**/*.ts",
        "./tools/**/*.ts",
        "!./node_modules/**",
        "!./modules_dart/**",
        "!./packages/**",
        "!./dist/**",
        "!./temp/**"
    ]
}

Erik Schilling

@Ablu

The first request in the list always seems to be the getProjectFileDetails

Erik Schilling

@Ablu

Ok. Now I have it hanging with getQuickFixes on top...

Erik Schilling

@Ablu

Reported #556 for this.

Tomas Trescak

@tomitrescak

Hello. In my old project Typescript is building files to a specific directory by preserving the file path. But, when I start a new project and I want to have the same behaviour, it is no longer the case. I have no idea, how can I make the same behaviour again :( For example: if file is in "client/myfile.ts" and my output is set to "dist", I want my file to appear in "dist/client/myfile.js". Do you have any idea please? This is my tsconfig.json:

{
"version": "1.5.0-beta",
"compilerOptions": {
"target": "es5",
"module": "commonjs",
"declaration": false,
"noImplicitAny": true,
"removeComments": false,
"noLib": false,
"preserveConstEnums": true,
"suppressImplicitAnyIndexErrors": true,
"outDir": ".tmp",
"watch": true
},
"filesGlob": [
"./src//*.ts",
"!./src/public//.ts",
"!./src/packages/*"
],
"files": [
"./src/client/src.ts"
]
}

Tomas Trescak

@tomitrescak

Nevermind, typescript compiler starts to produce those directories as soon as you add more files in diverse directories. Strange behaviour, but it works ;)

Basarat Ali Syed

@basarat

:rose:

Dandelion Mané

@decentralion

Can I disable autocomplete, or have it only activate when i Press cmd+space? I like it in principle but in practice it has a lot of issues: tends to insert NaN in random spots when I just want to put a newline, always is cluttered with tons of extra stuff like eval, parseInt, parseFLoat, when I am looking at a module with only a few members, blocks my view of nearby code.

It also tries to do autocomplete inside of comments (again, inserting NaN if I want a newline in the comment)

Basarat Ali Syed

@basarat

Can I disable autocomplete, or have it only activate when i Press cmd+space

@danmane can be controlled from autocomplete-plus package settings

@danmane :rose:

Dandelion Mané

@decentralion

Thanks! Would it be helpful for me to file issues on these autocomplete nuisances?

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

Micah Zoltu

@MicahZoltu

If I remember correctly, most of the annoyances with the auto-completer are due to the underlying auto-complete library.

Where communities thrive

People

Repo info

Activity