[
https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711360#comment-17711360
]
Jan Høydahl commented on SOLR-16465:
------------------------------------
Thanks for presenting your thoughts on the Developer Meeting yesterday! Useful
to sync up with the community before diving deep into a rabbit hole. Here are
the major questions / decision points I remember from the discussion:
# Should the new UI require a new server-side backend, or continue to be pure
SPA?
# Choice of framework: React with Next.js?
# The need for running old and new AdminUI in parallel for years? With need to
re-auth between them?
# Fresh start on App layout and page structure
# Integration with Solr's gradle build (briefly mentioned) vs a new repo?
I'll add my own initial thoughts on these in a followup comment
> Start the migration of the Admin UI to React
> --------------------------------------------
>
> Key: SOLR-16465
> URL: https://issues.apache.org/jira/browse/SOLR-16465
> Project: Solr
> Issue Type: Wish
> Components: Admin UI
> Reporter: Jeb Nix
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
