Angular 2 docs for ES6/7
github.com
Angular 2 docs for ES6/7
1–10 of 62 posts
Re: Angular 2 docs for ES6/7
#2I don't see a problem here, we've know Typescript is core here from the beginning.
Re: Angular 2 docs for ES6/7
#3I don't see a problem here, we've know Typescript is core here from the beginning.
I agree
Re: Angular 2 docs for ES6/7
#4I say good. One of the next tasks I'm going to take, as soon as I get some free time, is to integrate TypeScript into our front-end and start adding in interfaces and parameter types. I'm usually working on the back-end, but get drafted into the UI-side once in a while. The number of stupid little errors caused by typos or not having decent intellisense is troubling. Compared to the level of tooling and safety I'm used to on the back-end, it feels like banging rocks together.
Especially when we've got a gulp build process that takes long enough to run that I want to start some XKCD chair-jousting matches between edits.
Re: Angular 2 docs for ES6/7
#5ES6 is next version of ES5 so whatever works for ES5 should work for ES6, no need for special DOC for that.
Re: Angular 2 docs for ES6/7
#6I wonder why; it seems weird to insist your users either use TypeScript or mentally translate it to es6. I would think allowing community members to write es6 docs would be a good way to get more involvement. ¯\_(ツ)_/¯
Re: Angular 2 docs for ES6/7
#7I say good. One of the next tasks I'm going to take, as soon as I get some free time, is to integrate TypeScript into our front-end and start adding in interfaces and parameter types. I'm usually working on the back-end, but get drafted into the UI-side once in a while. The number of stupid little errors caused by typos or not having decent intellisense is troubling. Compared to the level of tooling and safety I'm us…
I am sure that the clientside developers in your company will come to realize their mistake when they see your interfaces and level of tooling.
Re: Angular 2 docs for ES6/7
#8I say good. One of the next tasks I'm going to take, as soon as I get some free time, is to integrate TypeScript into our front-end and start adding in interfaces and parameter types. I'm usually working on the back-end, but get drafted into the UI-side once in a while. The number of stupid little errors caused by typos or not having decent intellisense is troubling. Compared to the level of tooling and safety I'm us…
Your gulp job sounds like the real issue. Use IntelliJ and that fixes a lot of the problems
Re: Angular 2 docs for ES6/7
#9After switching to TypeScript, I am not sure whether I will ever go back to JavaScript (after so many years of using JS). I don't use or like Angular2 - but I use React with TypeScript.
Even if we could use ES6 JavaScript in the browser, transpilation isn't going away completely because we need HTML, uglification, vendor-libs, etc to be brought in together before deploying to production.
WARNING: If you are starting off with React+Typescript, expect to bang your head for may be, a couple of days, to get that stuff working. However, once it does work, it saves much more time and effort
Re: Angular 2 docs for ES6/7
#10[deleted]