[
https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703188#comment-17703188
]
Eric Pugh commented on SOLR-16465:
----------------------------------
Thanks [~marcussorealheis]! For me to get behind another Admin UI, I think we
need to nail the basic tooling setup, the deployment process, the login
plumbing working, and pick a basic CSS template that we can all live with. If
that was all in place, then I'd be a LOT more excited about putting energy into
this effort. I'd really like something that uses a off the shelf CSS "Admin
Tool" template, as that I think it our biggest capablity gap.
This may be a good time to start this effort, since as the V2 API stuff comes
online, we may be able to use those APIs in a new admin ui, versus retro
fitting into the old one....
> 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
>
> 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
