@sebmck @kentcdodds ah I didn't know that there were multiple specs...
@bradlygreen any idea on this?
-
-
Replying to @OCombe
@OCombe@kentcdodds@bradlygreen no idea, most likely follows the one being proposed as there has been collaboration with Angular on it.1 reply 0 retweets 1 like -
Replying to @sebmck
@sebmck@kentcdodds@bradlygreen well I guess I'll have to try then :)1 reply 0 retweets 0 likes -
Replying to @OCombe
@OCombe@sebmck@bradlygreen BOOM: http://babeljs.io/repl/#?experimental=true&evaluate=true&loose=true&spec=false&playground=true&code=import%20%7BComponent%2C%20Template%2C%20EventEmitter%7D%20from%20'angular2%2Fangular2'%3B%0Aimport%20%7Bbind%7D%20from%20'angular2%2Fdi'%3B%0Aimport%20%7Bglobal%7D%20from%20'angular2%2Fsrc%2Ffacade%2Flang'%3B%0A%0Aconst%20store%20%3D%20global.localStorage%3B%0Aconst%20axiosService%20%3D%20bind(axios).toValue(axios)%3B%0A%0A%40Component(%7B%0A%20%20selector%3A%20'sign-in'%2C%0A%20%20services%3A%20%5BaxiosService%5D%0A%7D)%0A%40Template(%7B%0A%20%20inline%3A%20%60%0A%20%20%20%20%3Cform%20(submit)%3D%22login(%24event%2C%20username.value%2C%20password.value)%22%3E%0A%20%20%20%20%20%20%3Cinput%20type%3D%22text%22%20placeholder%3D%22Username%22%20%23username%20value%3D%22kentcdodds%22%3E%0A%20%20%20%20%20%20%3Cinput%20type%3D%22password%22%20placeholder%3D%22Password%22%20%23password%20value%3D%22iliketwix%22%3E%0A%20%20%20%20%20%20%3Cbutton%20type%3D%22submit%22%3ESign%20In%3C%2Fbutton%3E%0A%20%20%20%20%3C%2Fform%3E%0A%20%20%60%2C%0A%20%20directives%3A%20%5B%5D%0A%7D)%0Aexport%20class%20SignIn%20%7B%0A%20%20constructor(%24http)%20%7B%0A%20%20%20%20this.%24http%20%3D%20%24http%3B%0A%20%20%20%20this.apiBase%20%3D%20'http%3A%2F%2Fapi.jwtftw.dev%3A3000%2F'%3B%0A%20%20%20%20this.store%20%3D%20store%3B%0A%20%20%20%20this.tokenKey%20%3D%20'user-token'%3B%0A%20%20%20%20this.loginSuccess%20%3D%20loginSuccess%3B%0A%20%20%7D%0A%0A%20%20login(event%2C%20username%2C%20password)%20%7B%0A%20%20%20%20event.preventDefault()%3B%0A%20%20%20%20this.%24http(%7B%0A%20%20%20%20%20%20url%3A%20this.apiBase%20%2B%20'login'%2C%0A%20%20%20%20%20%20method%3A%20'POST'%2C%0A%20%20%20%20%20%20data%3A%20%7B%0A%20%20%20%20%20%20%20%20username%3A%20username%2C%0A%20%20%20%20%20%20%20%20password%3A%20password%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D).then(response%20%3D%3E%20%7B%0A%20%20%20%20%20%20this.store.setItem(this.tokenKey%2C%20response.data.token)%3B%0A%20%20%20%20%20%20this.loginSuccess(response.data.user)%3B%0A%20%20%20%20%7D)%3B%0A%20%20%7D%0A%7D …1 reply 3 retweets 7 likes -
Replying to @kentcdodds
@OCombe@sebmck@bradlygreen NOTE: This does NOT mean that you can easily replace traceur (or TypeScript 1.5) with babel sadly.1 reply 0 retweets 0 likes -
Replying to @kentcdodds
@OCombe@sebmck@bradlygreen babel is missing types (needed by DI I believe) and parameter annotations (needed by EventEmitter).2 replies 0 retweets 0 likes -
Replying to @kentcdodds
@OCombe@sebmck@bradlygreen actually, babel doesn't have a problem with types it looks like. They're just ignored: http://babeljs.io/repl/#?experimental=true&evaluate=true&loose=true&spec=false&playground=true&code=function%20foo(hi%3Astring)%20%7B%0A%20%20console.log(hi)%3B%0A%7D%0A%0Afoo(1)%3B%0A …1 reply 0 retweets 0 likes -
Replying to @kentcdodds
@kentcdodds@sebmck@bradlygreen yes types are optional anyway, but in the end even if the compilation works, the code doesn't once executed1 reply 0 retweets 0 likes -
Replying to @OCombe
@OCombe@kentcdodds@sebmck Totally right. Some folks will not want to use types. This is a perfect option for them.1 reply 0 retweets 0 likes -
Replying to @bradlygreen
@OCombe@kentcdodds@sebmck Still, would be awesome if Babel supported types too. :)2 replies 0 retweets 1 like
@bradlygreen @OCombe @kentcdodds Maybe in the future :) Right now our focus is on delivering an extremely polished ES6 experience
-
-
Replying to @sebmck
@sebmck@OCombe@kentcdodds a perfectly worthy endeavor. I wouldn't want it differently in the timeline.0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 