[
https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618882#comment-17618882
]
Eric Pugh commented on SOLR-16465:
----------------------------------
I would love to see a PR with the ngUpgrade integrated.. There feels like
there is enough consensus in the community that the Admin UI isn't going to be
ejected as a separate effort. In that case, we have to figure out a path
forward for our Angular1.. So... Angular2 seems to be the logical path
forward.. Maybe not the "best", but good enough for what we need. Please tag
me on anything related to the Admin UI.
> 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]
