[
https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621423#comment-17621423
]
Jeb Nix commented on SOLR-16465:
--------------------------------
Incremental migration to React is much better. Great idea (I really didn't know
about the option). Indeed starting to pull this off on the first PR is the
hardest part here. I also agree that Solr needs the features and not the tools,
but I'm afraid from the day that the Admin UI will become somewhat untouchable
since we won't be able to migrate it or implement new features easily because
of a lack of modernism. Also, it is important to note that when speaking on UI
apps, keeping the app with good UX and good-looking pages is always a great
improvement. I'll try to play with the React migration stuff and give an update
as soon as things will progress
> 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]
