[
https://issues.apache.org/jira/browse/SOLR-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upayavira updated SOLR-7579:
----------------------------
Attachment: SOLR-7579.patch
Both parts resolved, I hope.
Firstly, the 'chosen' library was making the drop down too narrow, for reasons
I did not fathom. I took the hacky approach of fixing the width to 130px. Less
than perfect, but better than what was there.
Secondly, I added code to store the analysis parameters in the URL some time
after implementing the analysis tab initially. What I didn't fully appreciate
is the fact that Angular re-renders the view (rerunning the controller) once
you change the URL. This meant that a heap of parameters were set correctly,
then the view would reload without them. Some reasonable moving about should
have resolved this. When the user clicks the "analyse" tab, all that happens is
the URL is rewritten. Then, when Angular reloads the view, the view
initialisation causes the actual analysis work to happen.
> Angular admin UI core analysis screen field name/type dropdown issues
> ---------------------------------------------------------------------
>
> Key: SOLR-7579
> URL: https://issues.apache.org/jira/browse/SOLR-7579
> Project: Solr
> Issue Type: Bug
> Components: UI
> Reporter: Erik Hatcher
> Assignee: Upayavira
> Fix For: 5.2
>
> Attachments: SOLR-7579-schema.json, SOLR-7579.patch, screenshot-1.png
>
>
> field name/type drop-down too narrow and unusable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
