[WIP] Angular 2 Migration Preparation(Draft) about manageiq-ui-classic

[martinpovolny]

@AparnaKarve, @h-kataria, @hstastna : can you, please, read/comment this? We need to make sure that we don't introduce new obstacles for Angular 2 in our own PRs as well as in review.

From my point of view the Angular 1.x Best Practices are critical for us so that with each PR we don't increase the amount of work that will have to be done to get to Angular 2.

Thx!

[mtho11]

Angular 2 integration with Rails as a standard option is now feasible: https://github.com/rails/webpacker#ready-for-angular-with-typescript

[himdel]

Nice, so I guess we'll have to go rails 5.1 first, but hopefully that's the plan anyway.

[ZitaNemeckova]

React was chosen over Angular 2/4.

@miq-bot close_issue

[mtho11]

@martinpovolny here is the starter Angular 2 migration issue; feel free to edit...
CC: @himdel @skateman @dclarizio @karelhala

[mtho11]

From @skateman on December 13, 2016 7:22

@mtho11 actioncable already works well in SSUI and I don't think there will be any compatibility issues with ng2

[mtho11]

From @himdel on December 13, 2016 12:13

@mtho11 great list.. just adding some random thoughts.. :)

For point one (yarn), we already have ManageIQ/manageiq#12581

And, maybe you mean it that way, but.. I'd rather do the webpack transition in this release, separate from any Angular 2 efforts. So that we don't move to webpack & angular 2 at the same time :).

And agreed we definitely need to look into webpacker since it will be the default in rails 5.1.

Another thing, ngUpgrade should probably never get into a production build. Meaning we should ideally start right after fine gets its own branch, and finish before an RC.

Probably agreed on the UI router, although since we're still not using any frontend routing, if at that point we still don't, it may make sense to go with the new default router.. Especially since 1.6 should have a router closer to ng2..

And i18n may be a toughie.. but some gettext version will exist :).

[mtho11]

@himdel sounds like a smart thing to do webpack in this release so like you said to "isolate the Angular 2 efforts".

[mtho11]

From @himdel on December 19, 2016 21:37

10. Rx.js version moves from 4 to 5 with ng2 and the syntax changes quite a bit
    Does our limited existing ngrx stuff still work?

Created ManageIQ/manageiq#13255 to address the rx update (but depends on npm)

[mtho11]

From @dclarizio on January 12, 2017 22:34

@mtho11 can you please close this and reopen on the ui-classic repo? Thx, Dan

[mtho11]

FYI: this issue was migrated from manageiq repo with comments intact via:
https://github-issue-mover.appspot.com/

[hstastna]

I've read this list and I like it. If there will be something to add to the list from my point of view, I will do it.

[martinpovolny]

@himdel, @skateman, @AparnaKarve : ^^^

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!