[jira] [Commented] (SOLR-16465) Start the migration of the Admin UI to Angular

["Jan Høydahl (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632313#comment-17632313 ] 

Jan Høydahl commented on SOLR-16465:
------------------------------------

Wdyt [~epugh] , would it be feasible to arrange a hackaton or similar where the goal is to arrive at a branch with a POC for Admin UI where you can do {{'yarn run'}} and get the AdminUI served as a mix of Angular and React (just a few pages migrated)? Having such a starting point is the hardest part, then others can contribute migration of one screen at a time...

> Start the migration of the Admin UI to Angular
> ----------------------------------------------
>
>                 Key: SOLR-16465
>                 URL: https://issues.apache.org/jira/browse/SOLR-16465
>             Project: Solr
>          Issue Type: Wish
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Admin UI
>            Reporter: Jeb Nix
>            Priority: Major
>
> I suggest using [ngUpgrade|https://angular.io/guide/upgrade#upgrading-with-ngupgrade] to start a linear migration process to Angular from Angular JS. ngUpgrade will reach the end of life at the end of 2023, so we will only get a year of using it seamlessly, but this seems to me like the last resort regarding a linear migration of the Admin UI codebase. The need for this is of course to migrate the current Admin UI project to newer technology, instead of writing it all from the start (or implementing the same stuff once more in YASA).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org