nick-boss-tech commented on code in PR #5370:
URL: https://github.com/apache/solr/pull/5370#discussion_r4656424251
##########
solr/core/src/java/org/apache/solr/handler/designer/SchemaDesignerConfigSetHelper.java:
##########
@@ -585,6 +589,35 @@ ManagedIndexSchema loadLatestSchema(String configSet) {
return loadLatestSchema(loadSolrConfig(configSet));
}
+ List<Language> listAvailableLanguages() throws IOException {
+ if
(!cc.getConfigSetService().checkConfigExists(MULTILINGUAL_CONFIGSET_NAME)) {
+ return List.of();
+ }
+ return
loadLatestSchema(MULTILINGUAL_CONFIGSET_NAME).getFieldTypes().values().stream()
Review Comment:
🤖 *AI text below* 🤖
Existing Designer schemas can use `cz` for Czech, while `_multilingual`
supplies `cs`. When a user changes the language selection, the old `cz` value
has no matching option. The sync can then remove `text_cz` and `*_txt_cz` if no
explicit field uses the type. Could the selector preserve the legacy choice for
existing schemas?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]