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

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

Thanks for caring for the Admin UI. I think some of us have stopped hoping 
after so many reboots that just faded. I can see how an incremental approach is 
less likely to fail. But someone still needs to do the first PR, port one page 
over and document how to do it for others to be able to contribute. What is you 
thought on how that could happen?

Also, even if I'm not a frontend guy, I have understood that a migration to 
e.g. React is also possible in an incremental fashion, see 
[https://buttercms.com/blog/migrating-from-angularjs-to-react/] and similar 
blogs. React would of course be a superior choice since it has many fold 
develper attention and popularity. The left-menu and the "Login" parts of 
AdminUI will need to be bridged between the two, but once you have wired up 
react, you can start replacing screen by screen.

But at the end of the day, it is more important for Solr that the job gets done 
than with what exact tools.

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to