Step forward

Question

Step forward

m0t0r opened this issue 9 years ago · 13 comments

Hey guys, I hope I will get more free time soon and get back to this project. I wanna know what do you think we should choose as a step forward for the project.

Well, I am talking about tree options:

We just upgrade up to angular 1.4, as a big part of which is a new API for animations.
We're taking step 1 and adding ES6 with its sweet features.
We're moving even more further and considering to use TypeScript, with its power.

As the code base is really small at this moment but new tech is actively coming we probably need to discuss about plans for the future.

I'd vote for the second option.

Please, share your thoughts

Answer 1 · 2015-05-15T04:27:07.000Z

I would go for TypeScript because of the type system. And it's supposed to be aligned with es6 anyway.

Answer 2 · 2015-05-18T07:48:18.000Z

What do you think about merging directives from https://github.com/angularify/angular-semantic-ui (with permission)?

Answer 3 · 2015-05-20T02:25:32.000Z

I think that we do not have plans to merge that project into the current one. @caitp, need your input here as well and also on the issue topic.

Answer 4 · 2015-05-20T02:28:25.000Z

@stevesherrie's and @mxth's thoughts are required here as well

Answer 5 · 2015-06-03T23:17:14.000Z

We are planning to move forward towards ES6

Answer 6 · 2015-06-04T01:14:27.000Z

TypeScript's alignment with es6 is sort of questionable at this time (the lack of ClassExpression support makes unit testing a major pain). I would hold off on that until angular2 is a bit more stable and it looks worthwhile porting stuff to angular2.

As for ES6, browser support is a bit of an issue, although we are steadily working to improve this. 1.x angular apps may need to support earlier browsers than Chrome 46 or MS Edge though.

I would say for semantic-ui-angular, stick to ES5, which is reasonably trustworthy.

Answer 7 · 2015-06-04T02:38:51.000Z

@caitp it was assumed to have code base in ES6 and transpile it down to ES5 for the browsers support. I do not see actual reasons to stick with ES5 (as the code base is pretty small) when we can prepare code to be compatible with older browsers and look to the future when there not going to be a need to transpile anything.

Answer 8 · 2015-06-04T04:41:20.000Z

Yeah I'd rather not do that just because it doesn't really gain anything, and the dev ops just aren't worth it

Answer 9 · 2015-06-04T11:15:18.000Z

Note that if we follow ES6 (ES7 also?) we can use these components easily on http://aurelia.io/ too.

Answer 10 · 2015-10-23T04:01:20.000Z

Hey peoples. I've become involved with a project that's using Semantic UI and AngularJS so I can actively contribute to this project moving forward.

I vote for Angular 1.4 update with ES6 features.

I would also like to hear what our goals are and milestones we can set up to achieve.

Cheers!

Answer 11 · 2015-11-27T22:58:10.000Z

I'm thinking in some like: https://github.com/AngularClass/NG6-starter

Answer 12 · 2015-11-30T00:07:58.000Z

What we have to do to move things forward?
ES6 features will solve all problems?

Answer 13 · 2015-12-09T20:00:33.000Z

closing all issues and PR for a while. Restarting project roadmap