algoliasearch-client-scala
algoliasearch-client-scala copied to clipboard
algolia
⚡️ A fully-featured and blazing-fast Scala API client to interact with Algolia.
Would it be possible to provide scala3 artifacts for the algoliasearch-client?
We need to add support for the [`enableReRanking`](https://www.algolia.com/doc/api-reference/api-parameters/enableReRanking/) query parameter at search time.
We've recently discovered that at least one API client was exposing "eu" as a valid region for the Analytics client implementation, which is wrong. Only the following regions are available...
It was discovered that the Algolia Search API is sometimes returning the `ignorePlurals` field from a Query Rule's consequence params field as a string, such as: ```json "consequence": { "params":...
Based on the one from the [Ruby client](https://github.com/algolia/algoliasearch-client-ruby/blob/master/CONTRIBUTING.MD), update contributing guide so it's easier for external contributors to collaborate.
- Algolia Client Version: 1.39.1 - Language Version: ### Description Algolia uses parameter `clickAnalytics` to return `queryID` in response. Description of `clickAnalytics`: https://www.algolia.com/doc/api-reference/api-parameters/clickAnalytics/ Description of `queryID` in response: https://www.algolia.com/doc/api-reference/api-methods/search/#method-response-queryid Unfortunately...
Quick refactoring: the `IndexingDsl` trait is currently written within the `IndexingDefinition.scala` file of the `definitions` package but it should be migrated to the `dsl` package, like all other `*Dsl` traits.
On top of the existing `objectID` (singular) string field, a new `objectIDs` (plural) string array field is now be exposed in the `rule.consequence.promote` Rule object representation. This lets the user...
The `restrictSources` of API keys should be typed as: - a comma-separated string This parameter does **not** support array of strings as a valid type.
The `restrictIndices` of API keys should be typed as: - an array of strings OR - a comma-separated string Both format should be handled at serialization/deserialization time.