[
https://issues.apache.org/jira/browse/SOLR-17924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097750#comment-18097750
]
Christos Malliaridis commented on SOLR-17924:
---------------------------------------------
Sorry for the late reply, I couldn't find much time before to track the issues.
> Can those names be changed to use consistent capitalization? (or all
> lowercase with/hyphens)
[~hossman] I think we have not determined a capitalization rule here, so we
should do that first and then proceed with updating all entries. For lowercase
vs. hyphens, Using capital letters makes it more readable, hyphens become dots
in the usage and is not ideal in some cases, where when using lowercase where
capital letters are currently used is also fine by me. Not sure which
convention is used msot in the file, but I would simply go with that.
> If it's a matter of "don't care"
Backports in the admin UI are simple, as long as the dependencies that are
required are aligned first. In this case I think Jan updated some Admin UI
dependencies and didn't backport them, so I would have to backport these
dependency updates first in order to backport this one as well. So we decided
that if we plan to backport in bulk, we would include both changes. I don't
remember which PR it was, but I can pick that out and backport if you want. :)
> Create Configset Dialog
> -----------------------
>
> Key: SOLR-17924
> URL: https://issues.apache.org/jira/browse/SOLR-17924
> Project: Solr
> Issue Type: Sub-task
> Components: Admin UI
> Reporter: Christos Malliaridis
> Assignee: Christos Malliaridis
> Priority: Major
> Labels: new-ui, newdev, pull-request-available, ui
> Fix For: main(11.0)
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In the configsets section of the new UI the user should be able to add a new
> configset.
> h2. Task
> Implement the configset dialog that allows the user to create a new configset
> and that uses existing configsets.
> h2. Acceptance Criteria
> - The user can insert a name for the new configset
> - The user can choose a base configset from the existing configsets
> - The dialog's dropdown for selecting a configset may use the currently
> selected configset from the Configsets section as default
> - The default configset (_default) is selected by default
> - When the configset is successfully created and the dialog is closed, the
> ConfigsetsComponent from the section updates its current selection options
> and selects to the new congiset
> - The dialog is closed if the configset is created successfully
> - The dialog shows the error if a configset could not be created for some
> reason
> - The configset name is validated with the existing configsets
> - existing name conflicts are shown as error in the input field
> - no request is sent in case of a conflict
> You should not implement hte configset import feature that is currently
> present in the designs, as this will be a separate task.
> h2. Additional Information
> The existing ConfigsetsComponent interface may be reused and the
> DefaultConfigsetsImplementation may be updated if used and changes are
> necessary. Avoid code duplication if the same functionality is in the
> existing components (e.g. configset selection dropdown).
> For the edge-case where no configsets are available (not even _default) a
> request should be sent without a baseConfigset set. If the missing default
> configset triggers an error it should be shown to the user. No further error
> handling has to be implemented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
