Skip to content

TypeScript 1.4 #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
yukulele opened this issue Jan 17, 2015 · 9 comments
Closed

TypeScript 1.4 #16

yukulele opened this issue Jan 17, 2015 · 9 comments

Comments

@yukulele
Copy link

ArcticTypescript is not compatible with TypeScript 1.4 new features:

Union Type:

function foo(bar: string|number ){ /* */ }

Template Strings:

return `My name is ${firstname} ${lastname.toUpperCase()}`

And more...
http://blogs.msdn.com/b/typescript/archive/2015/01/16/announcing-typescript-1-4.aspx

@yukulele yukulele changed the title Typescript 1.4 TypeScript 1.4 Jan 17, 2015
@Phaiax
Copy link
Owner

Phaiax commented Jan 20, 2015

https://github.com/clausreinke/typescript-tools

This is what ArcticTypescript is using and what defines the binding to the actual used typescript version. It seems like the author clausreinke is planning to update to Typescript 1.4:

clausreinke/typescript-tools#39

But this is a bunch of work as you can see, so don't expect this to be done immediately.

@pocesar
Copy link

pocesar commented Jan 25, 2015

👍

1 similar comment
@IlanFrumer
Copy link
Contributor

👍

@Phaiax
Copy link
Owner

Phaiax commented Feb 5, 2015

I have included the new typescript-tools and the dev branch now supports typescript 1.5.

My current problem is the configuration of the typescript services (ES5/6, ..). With typescript 1.5, another compiler configuration option via a tsconfig.json file has been introduced, and the typescript-services support this file as well:

https://github.com/TypeStrong/tsconfig

I would like to move the configuration from the .sublime-project and .sublimets file to only support tsconfig.json. The config in this tsconfig.json file would be used from the codecompletions stuff as well as from the included build system. (and other editors too)

But they are still investigating and changing the style of tsconfig.json (file blob, ..):

https://github.com/Microsoft/TypeScript/issues?q=is%3Aissue+is%3Aopen+tsconfig

I'm not completely sure on where to put the other settings (build_on_save, ..) (most of them are user related, so they can move into .sublime-project or some other config file in the sublime config folder.

But where will i put the pre_processing_commands and post_processing_commands? I'm not sure if i should put this into tsconfig.json or drop support for these options.

IMO, very simple projects do not need these options, and for bigger and more complicated projects they are not sufficient. Those projects will use grunt/jake/make anyway, so there would be no need for a build system with pre_processing_commands support in ArcticTypescript.

The other thing is, I would recommend to use tsc with --watch anyway.

If you do not raise your hand, I may drop those options.

As soon as I have decided what to do, I will continue to work on.

@AdamPD
Copy link

AdamPD commented Feb 6, 2015

Strange - whenever I checkout the dev branch, I start getting errors.

@IlanFrumer
Copy link
Contributor

F1 not working , I get this error:

Traceback (most recent call last):
  File "/home/ilan/.config/sublime-text-3/Packages/ArcticTypescript/lib/system/AsyncCommand.py", line 148, in <lambda>
    sublime.set_timeout(lambda:self.result_callback(tss_answer, **self.callback_kwargs),000)
  File "/home/ilan/.config/sublime-text-3/Packages/ArcticTypescript/lib/Commands.py", line 64, in async_react
    liste = types['docComment'].split('\n')+[kind+' '+types['fullSymbolName']+' '+types['type']]
KeyError: 'fullSymbolName'

@Phaiax
Copy link
Owner

Phaiax commented Mar 7, 2015

Current dev branch is next_big_thing

Some todos to do, but its almost finished

@IlanFrumer
Copy link
Contributor

Good job. Everything works great for me now. 👍

@Phaiax
Copy link
Owner

Phaiax commented Mar 12, 2015

new version 0.6.0 is out. If you switched to next_big_thing, i would recommend you to go back to package control, since next_big_thing is not active anymore.

One thing what is missing is syntax highlighting for let, type and template strings, but this will be implemented in the next version.

I will close this for now.

@Phaiax Phaiax closed this as completed Mar 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants