[
https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618186#comment-17618186
]
Jeb Nix edited comment on SOLR-16465 at 10/15/22 11:22 PM:
-----------------------------------------------------------
This will enable us to declare some rules regarding the future development of
the Admin UI. Rules such as "AngularJS-based PRs for new components won't get
approved" will drastically help with the migration process of the web app.
was (Author: JIRAUSER296760):
This will enable us to declare some rules regarding the future development of
the Admin UI. Rules such as "AngularJS-based PRs for new components won't get
approved" will drastically help with the migration process of web app.
> 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]
