[
https://issues.apache.org/jira/browse/SOLR-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437447#comment-16437447
]
Alexandre Rafalovitch commented on SOLR-12196:
----------------------------------------------
>From all I have read, the migration from Angular 1 to later version is a real
>piece of re-engineering as well. In that sense, migrating to React or Vue are
>probably the projects of similar complexity.
My vote would probably be for React as there are still more integrations with
it and more possibilities (native mobile UI with React Native!?!).
And given the amount of work, I wonder if that's also a good time to collect
larger level ideas on what UI should look like, given the prominence of
Javascript and availability of self-descriptive and management Solr APIs.
> 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
