I've felt we need one or two less maybe. MultiMapSolrParams can often
be substituted by ModifiableSolrParams. Javadocs could be improved in
general.
RequiredSolrParams and DefaultSolrParams (plus subclasses) could be
package scope so as to discourage direct use, which I think is never
needed.
O
[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]
Dear community,
We hope you are doing great, are you ready for Community Over Code EU?
Check out the featured sessions, get your tickets with special
discoun
I agree that things are needlessly complex, and could definitely be
simplified. (hopefully down to one class?)'
- Houston
On Wed, Apr 3, 2024 at 9:54 AM Gus Heck wrote:
> Ah, just noticed that I missed the ! symbol when I read that code, none the
> less things are still complex
>
> On Wed, Apr
Ah, just noticed that I missed the ! symbol when I read that code, none the
less things are still complex
On Wed, Apr 3, 2024 at 10:50 AM Gus Heck wrote:
> We have quite a few, including MapSolrParams which seems to explicitly
> defy the contract of SolrParams being a multimap...
>
> Has anyone
We have quite a few, including MapSolrParams which seems to explicitly defy
the contract of SolrParams being a multimap...
Has anyone spent any time considering if we really need all these variants:
- AppendedSolrParams
- DefaultSolrParams
- DocRowParams
- MapSolrParams
- Modifiabl
Hi everyone,
As part of The ASF’s 25th anniversary campaign[1], we will be celebrating
projects and communities in multiple ways.
We invite all projects and contributors to participate in the following
ways:
* Individuals - submit your first contribution:
https://news.apache.org/foundation/entry
