gerlowskija commented on PR #4203: URL: https://github.com/apache/solr/pull/4203#issuecomment-4400577942
> other SchemaDesignerAPI endpoints that look like they could be replace with a ConfigsetsAPI call can't be because of Schema Designer specific business logic. Appreciate your writeup on this, thanks @epugh ! If we were designing this from scratch I'd argue some of this stuff should be built into the configset APIs themselves as a general-purpose concept. "Enabled/disabled" in particular seems like a good candidate in that regard. The configset-validation/testing is a bit trickier or more special-purpose, but still... Anyway, all of that is definitely out of scope for this PR. But thinking aloud in terms of deduplicating this API stuff down the road... Starting in on review now, will aim to do that from a purely "migration" perspective. -- 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]
