[ https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438072#comment-16438072 ]
Alexandre Rafalovitch commented on SOLR-12196: ---------------------------------------------- My feeling is that "if not now" will be "close to never". Because it was a huge effort to move it to Angular 1 and some bits were not even finished for very long time (ever?). So, let's say another 3 years before anybody will raise this conversation with the same amount of "sunk costs" as right now. As to how/who, yeah, that's the big issue. Has been, it seems for a long time. I am interested in learning React but I am not a frontend dev myself to take a lead. And certainly not a visual designer, which is the hairy part... But my feeling is that maybe it is worth asking on the dev list as a tradeoff discussion. > Prepare Admin UI for migrating to Angular.io > -------------------------------------------- > > Key: SOLR-12196 > URL: https://issues.apache.org/jira/browse/SOLR-12196 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Admin UI > Reporter: Jan Høydahl > Priority: Major > Labels: Angular, AngularJS, angular-migration > Fix For: master (8.0) > > > AngularJS is soon end of life, it [enters LTS in july > 2018|https://docs.angularjs.org/misc/version-support-status], whereupon it > will only receive fixes to serious bugs. Solr uses AngularJS 1.3 (the latest > AngularJS will be 1.7). > This issue is *not* for upgrading to Angular5/6, but to start preparing the > existing UI for easier migration later on. See > [https://angular.io/guide/upgrade]. > This JIRA will likely get multiple sub tasks such as > * Change to [Folders-by-Feature > Structure|https://angular.io/guide/upgrade#follow-the-angularjs-style-guide], > i.e. mix html, css, js in a folder based on feature > * Use a [Module > Loader|https://angular.io/guide/upgrade#using-a-module-loader] like > [Webpack|https://webpack.js.org/] > * Use [Component > Directives|https://angular.io/guide/upgrade#using-component-directives] > (requires first move from AngularJS 1.3 to 1.5) > The rationale for this lira is recognising how central the Admin UI is to > Solr, not letting it rot on top of a dying framework. Better to start moving > step by step and [perhaps write all new views in Angular > 5|https://angular.io/guide/upgrade#upgrading-with-ngupgrade], than to fall > further and further behind. > This effort of course assumes that Angular.io is the path we want to go, and > not React, VueJS or some other new kid on the block :) -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org