[
https://issues.apache.org/jira/browse/SOLR-12276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076173#comment-17076173
]
Marcus Eagan commented on SOLR-12276:
-------------------------------------
[~erickerickson][~jdyer] It looks like this ticket died some time ago. Is it
still around? I think a couple things we definitely need are hot reloading and
getting off the end-of-life framework.
I have experimented with doing some of this sort of conversion for the sake of
staying on top of things and helping front end engineers be productive. If this
is still a consideration, what's the best way to keep it going? Is it safe to
work off the current branch or should I open a new ticket. Please advise.
> Admin UI - Convert from "AngularJS" to "Angular"
> ------------------------------------------------
>
> Key: SOLR-12276
> URL: https://issues.apache.org/jira/browse/SOLR-12276
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Reporter: James Dyer
> Priority: Minor
> Labels: Angular, AngularJS, angular-migration
> Time Spent: 1h
> Remaining Estimate: 0h
>
> With SOLR-12196 it was noted the current Solr Admin UI runs AngularJS (1.x),
> which is to be End-of-Life later this year. Various options were proposed
> for what to do next. One option is to keep the existing functionality but
> migrate to a newer UI framework. This ticket is to migrate the existing UI
> to Angular (2+).
> See [this readme
> file|https://github.com/jdyer1/lucene-solr/tree/feature/angular-conversion-solr-admin/solr/webapp].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
