[
https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711410#comment-17711410
]
Jan Høydahl commented on SOLR-16465:
------------------------------------
# Backend process: To limit scope, would be nice if this was optional, i.e.
start with a pure static SPA. But would also be powerful to allow deploying
Admin UI as a separate app in the future.
# Framework: React is a no-brainer. But I wonder if Next.js is overkill. I
think it mainly targets larger web sites where Server-Side-Rendering (SSR) is
crucial for performance. But SSR requires a Node backend, which is unfortunate.
I think we are good as SPA with Client-Side-Rendering (CSR). Another potential
opinionated framework is [https://vitejs.dev|https://vitejs.dev/] which gives
opinionated selection of tooling, but much more light weight
# We may have to live with dual Admin UIs (as we had when migrating from
JQuery -> Angular). Perhaps existing Admin UI app can be adapted to receive
Auth info in the URL to avoid double login.
# New app layout: Would benefit from a professional page UX design. Can we
request design donation from users? Or funding to hire someone?
# Build: Suppose the react app should be in the 'solr' monorepo. And be able
to run in dev mode on localhost:NNNN, but when packaging the binary distro, it
is bundled up into html, css, js to be served by Solr.
> 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: [email protected]
For additional commands, e-mail: [email protected]
